[JBoss JIRA] Created: (JBIDE-3401) JMX tests are running, but no test cases found in core and ui suites
by Nick Boldt (JIRA)
JMX tests are running, but no test cases found in core and ui suites
--------------------------------------------------------------------
Key: JBIDE-3401
URL: https://jira.jboss.org/jira/browse/JBIDE-3401
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jmx
Affects Versions: 3.0.0.GA
Reporter: Nick Boldt
Assignee: Rob Stryker
I've added new AllTests classes to org.jboss.tools.jmx.core and org.jboss.tools.jmx.ui, borrowed from other EPL code in drools' tests. Unfortunately, the "find all my child test cases" suite does not find any tests to run. Can you take a look and either manually add the tests you want to run to a suite, or provide some other way to hook these tests into the build system?
Here's the error tracked by the build:
org.jboss.tools.jmx.core.AllTests.<init>
Failing for the past 2 builds (Since Unstable#1236 )
Took 0 sec.
Error Message
Failed to invoke suite():java.lang.Error: There are no test cases to run
Stacktrace
org.eclipse.test.EclipseTestRunner$TestFailedException: Failed to invoke suite():java.lang.Error: There are no test cases to run
at org.eclipse.test.EclipseTestRunner.runFailed(EclipseTestRunner.java:283)
(http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly/1...)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-3054) CSS Class Wizard UI improvements
by Max Rydahl Andersen (JIRA)
CSS Class Wizard UI improvements
---------------------------------
Key: JBIDE-3054
URL: https://jira.jboss.org/jira/browse/JBIDE-3054
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 3.0.0.beta1
Reporter: Max Rydahl Andersen
Fix For: 3.0.0.cr1
The CSS class editor is really useful now but I found a couple of glitches/suggestions while testing it:
1) When using the wizard directly please initialize the File and style based on the current selection so users don't have to browse hundreds of projects/directories
2) If used from the VPE editor and I don't specify a css or class and press Ok I get an exception; shouldn't it either generate internal style CSS in this case or at least require the user to fill in file and style fields
3) Used from the vpe it should give a dropdown with the included .css files if possible, again to avoid unecessary manual browsing
4) On new styles (style attribute is empty) it would be good to remember the previous editied external css
5) The preview area is blank at first; I need to touch a field to see a preview..and couldn't we take the first 50 characters from the selected tag instead of just having the default string ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months
[JBoss JIRA] Created: (JBIDE-3150) CSS Style Class Dialog possibilities
by Yura Zhishko (JIRA)
CSS Style Class Dialog possibilities
------------------------------------
Key: JBIDE-3150
URL: https://jira.jboss.org/jira/browse/JBIDE-3150
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 3.0.0.beta1
Reporter: Yura Zhishko
Assignee: Maxim Areshkau
First test case:
1) Open/create CSS file
2) Add next content:
.myClass1, .myClass2 {
background-color: red;
}
3) Save changes
4) Choose any componenet on the page that support styleClass attribute.
5) Click button opposite styleClass attribute in Properties view
ASSERT: CSS Style Class Dialog should appear
6) Choose changed CSS file
7) Check Style class and choose line with classes from Step 2
8) Press Ok
RESULT: new styleClass attribute appears with next content: myClass1,.myClass2
POSSIBLE SOLUTION: style classes should follow one by one, throw white spaces
Second test case:
1) Choose any component with styleClass attribute
2) Set up the value of styleClass attribute in source code
3) Click button opposite styleClass attribute in Properties view
ASSERT: CSS Style Class Dialog appears but we haven't any preload into Style class field
4) POSSIBLE SOLUTION: the value of styleClass attribute should be displayed in the Style class field
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 6 months