PaulHill
New Member
Joined 8 years ago
User Profile
User Widgets
Contributions
An output selection grid to limit requests output to files
When setting up a run of tests allow the user to apply a filter to the output to the log file allowing them to filter on 1. Duration 2. OK/Warning/Error 3. Ranges of Request ID/ Time period/ Call Types/ Machine/ Test/ and so forth This will reduce unwanted data, allow tests to be for longer before exceeding log file size limitations. In addition, when the data is exported, the data will be ready for processing and require less time to use.898Views0likes0CommentsAllow changes to the editing window layouts to be lockable for all requests, tests for a user
When editing a tests requests, allow the users to set up the screens as they need them for that session or user, and have a lock button so that for each request, the work area remains in the same configuration, so that they don't need to keep changing things around each time. A found in one session where I had to check every request I sent 20% of the time changing the environment around.1.7KViews1like1CommentAn export/import facility for tests be allow editing in another editor
This would allow the test to be edited with any common mass update facilities, without having to include them in LC. The import facility could then perform a validation to ensure that the test was compatible with the proprietary rules in LC and the tests could be used in their updated states. The validation routine could then add stamps to indicate: 1. It has been edited with ... <tool name>, date time stamp and reference the original test. 2. A Label to allow brief notes on what was done 3. A flag to indicate it has been externally edited, Not all required, but these would help in mixed test environments. Alternatively: Make tests editable with other editors directly (probably more difficult, and with less control of content).980Views0likes0Comments