Activity

From 07/24/2022 to 08/22/2022

11:45 AM Feature #6677: Performance test mode: I had a problem that all tests (all @TestSet@-s) were executed in parallel which generated a very high load and (whic... Tomasz Domin

01:31 PM Feature #6677: Performance test mode: Eric Faulhaber wrote:
> Sorry I'm late to the party, but I have a basic question: it seems one of the big challenges... Tomasz Domin
12:23 PM Feature #6677: Performance test mode: Sorry I'm late to the party, but I have a basic question: it seems one of the big challenges in re-purposing the exis... Eric Faulhaber
12:19 PM Feature #6677: Performance test mode: > Once PM methods are tested and work correctly they would replace old ones or would be merged with old ones to get l... Greg Shah
12:05 PM Feature #6677: Performance test mode: Greg Shah wrote:
> Code Review Revisions 23 and 24
> Overall, these are very good changes.
>
> 1. I wonder if ... Tomasz Domin
10:53 AM Feature #6677: Performance test mode: Code Review Revisions 23 and 24
Overall, these are very good changes.
1. I wonder if the @PM@ versions of metho... Greg Shah

05:01 PM Feature #6677: Performance test mode: Committed revision 24.
* Screen update processing optimization, time unit correction for waitForTimeout
* Fix for p... Tomasz Domin
11:19 AM Feature #6677: Performance test mode: Committed revision 23 with following changes:
* Implement test skip list feature
* Logging tweaks
* Correct value ... Tomasz Domin
05:45 AM Feature #6677: Performance test mode: Good. Greg Shah
01:30 AM Feature #6677: Performance test mode: Greg Shah wrote:
> What about tests which depend upon a database reset to occur before the tests run?
I consider da... Tomasz Domin
09:39 AM Feature #6265: generate junit-compatible xml results for output: Hi Greg, It's not much but is a clone of ReportGenerator.java, I attached the file. To include, I modified Harness.ja... Chris Weaver

02:12 PM Feature #6677: Performance test mode: What about tests which depend upon a database reset to occur before the tests run? Greg Shah
01:13 PM Feature #6677 (WIP): Performance test mode: Tomasz Domin
01:13 PM Feature #6677: Performance test mode: The basic assumption is to try to reuse existing regression test scenarios to emulate real-life application behavior ... Tomasz Domin

07:11 AM Feature #6677: Performance test mode: For some major changes introduced to the system there is a need to check how the change affects overall performance o... Tomasz Domin
06:10 AM Feature #6677 (WIP): Performance test mode: Tomasz Domin
05:42 AM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: I have no objection to this idea. However, it probably should be implemented in a new task. Greg Shah
05:17 AM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: Some ideas about how to make a kind of benchmark with @harness@
# use exiting scenarios to get more real-world like ... Tomasz Domin

11:43 AM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: Code Review Rev 22
1. In @ExitCode@, please set @PRE_FAILED@ to -13 instead of -12 (which is a duplicate error num... Greg Shah
10:58 AM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: Added logging of progress of test plan every 60 seconds:... Tomasz Domin

03:23 PM Feature #6265: generate junit-compatible xml results for output: Chris: Can you post your code that implements this feature? I'd like to start with it. Greg Shah
03:22 PM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: Code Review Revision 21
No objections. Greg Shah

10:28 AM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: Greg Shah wrote:
> Code Review Revisions 19, 20
>
> Overall, I like the changes.
>
> 1. In @build.xml@, are bo... Tomasz Domin

01:07 PM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: Code Review Revisions 19, 20
Overall, I like the changes.
1. In @build.xml@, are both of these conditions neede... Greg Shah
11:06 AM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: Implemented @TestSet@ abort when early initialization of @Test@ fails - in that case the entire @TestSet@ queue is ab... Tomasz Domin

01:15 PM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: Committed revision 19. Tomasz Domin
12:48 PM Feature #1554: enhance the command-line to provide better user feedback on the state of testing: I've implemented two features:
- dumping reports on CTRL-C - so partial results are available for review in case tes... Tomasz Domin
12:39 PM Feature #1554 (WIP): enhance the command-line to provide better user feedback on the state of tes...: Tomasz Domin

Also available in: Atom

Harness