Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "WTP Performance Tests/2008-09-15"
m |
|||
| Line 39: | Line 39: | ||
== Minutes == | == Minutes == | ||
| − | : | + | ;Has every team identified a single test case? |
| + | :Common Tools and JSF Tools teams are not ready yet. | ||
| + | |||
| + | ;Do we have success on running the performance test procedure on the a single test? | ||
| + | :Not really! Kaloyan has tried to run the CSS UI test suite, because it contains only a single test case. The test itself completes correctly, but the step with the graph generator fails again - Java returned: 13. There is no output or any logs to look at. The org.eclipse.test.performance plugin is patched as suggested by Nick. | ||
| + | :The problem could be that the CSS UI test suite does not produce graphs on principle, or because there is no baseline yet. Nick will send guidelines on how to run the graph generator. | ||
| + | |||
| + | ;Best practices for writing Eclipse performance tests | ||
| + | :Mark has taken a look at the Eclipse Performance HowTo. He told that the main graph on the performance results page is a result summary where each test suite should contribute. At the moment some test suites do, but other don't. We have agreed that this has to be done, but let us first run the simpler things. | ||
== Action items == | == Action items == | ||
| − | : | + | :Nick will send mail with instructions how he had successfully run the graph generator. |
| + | :Kaloyan will proceed trying running the performance test procedure. | ||
== References == | == References == | ||
:Bugzilla: (performance tests) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=244986 No Results for WTP Tests] | :Bugzilla: (performance tests) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=244986 No Results for WTP Tests] | ||
Latest revision as of 12:55, 15 September 2008
Attendees
| Gary Karasiuk | |
| Angel Vera | Y |
| Mark Hutchinson | Y |
| Nick Sandonato | Y |
| Carl Anderson | Y |
| Kaloyan Raev | Y |
| Raghu Srinivasan | |
| Neil Hauge | Y |
| David Williams | Y |
Agenda
- Has every team identified a single test case?
- Do we have success on running the performance test procedure on the a single test?
- Best practices for writing Eclipse performance tests
Minutes
- Has every team identified a single test case?
- Common Tools and JSF Tools teams are not ready yet.
- Do we have success on running the performance test procedure on the a single test?
- Not really! Kaloyan has tried to run the CSS UI test suite, because it contains only a single test case. The test itself completes correctly, but the step with the graph generator fails again - Java returned: 13. There is no output or any logs to look at. The org.eclipse.test.performance plugin is patched as suggested by Nick.
- The problem could be that the CSS UI test suite does not produce graphs on principle, or because there is no baseline yet. Nick will send guidelines on how to run the graph generator.
- Best practices for writing Eclipse performance tests
- Mark has taken a look at the Eclipse Performance HowTo. He told that the main graph on the performance results page is a result summary where each test suite should contribute. At the moment some test suites do, but other don't. We have agreed that this has to be done, but let us first run the simpler things.
Action items
- Nick will send mail with instructions how he had successfully run the graph generator.
- Kaloyan will proceed trying running the performance test procedure.
References
- Bugzilla: (performance tests) No Results for WTP Tests