The TestMaker development community is working on a refactoring of the TestNode software. Below is a list of the improvements we intend to make. We are looking for your feedback on the list: Are the items on the list important to you? Which improvements stand out as the most important to you? If the list is missing something then please let us know. Thanks, in advance.
TestNode Refactoring List (In order of priority):
1) TestNode stability. TestNode runs TestScenarios in crash-proof processes. If the test crashes the TestScenario the TestNode remains running and can run another TestScenario. When a TestScenario crashes the current set of transaction logs is still available to the console. Prevent TestNode from stopping even if a transaction invokes System.exit(0). TestNode preferences control the number of concurrently running TestScenarios; Default is 1.
2) TestNode should have logs folder, where agents can saves log files, and this folder should be sent to the console. TestNode should deny an agent trying to save or modify files outside the logs folder.
3) TestNode should have a status web page and REST interface (Current scenario, threads, time left to process scenario, log files)
4) Refactor the control runner to make it easier to add new ScriptRunners.
5) MultiLoad, a load test that has multiple levels of virtual users without a rampdown-up between
6) Re-enable Shock Test
7) Run TestNode as a Windows service (
www.jpackages.com/execj/)
Jar files in a scenario should work like they were in the bootstrap classpath
9) TestNode should be able to start viral start up.
10) TestNode should have credential system (Currently is an open door)
Please give us your feedback. Thanks!
