Opened 13 years ago
Closed 13 years ago
#8908 closed enhancement (fixed)
Possiblity to change test case status from the tree view
| Reported by: | Jouko Korhonen | Owned by: | Roberto Longobardi |
|---|---|---|---|
| Priority: | normal | Component: | TestManagerForTracPlugin |
| Severity: | major | Keywords: | |
| Cc: | Trac Release: | 0.12 |
Description
The possiblity to change the statuses already in the tree view without opening the test case would make the testing a lot faster (especially when a slow connection, like for example when the Trac server is located in different continent than where the Testing team is working) if one could change the test result directly from the tree view that is listing the test cases.
This is the case especially when the testers do know the test cases by heart. (Or are using separate test cases tracking and do only report the results into the plugin)
One additional way might be a possibility to set the whole (sub)catalog of test cases into selected status. (However this may lead to a misusage, like first setting all passed and then just setting the one failed -> leading to a wrong status to be marked on the test case status history, unless there would be a timer (for example 15sec) to keep a track of 'mistakes' when setting the statuses and keeping the test case status history 'clean' )
Attachments (1)
Change History (4)
comment:1 Changed 13 years ago by
comment:2 Changed 13 years ago by
| Status: | new → assigned |
|---|
Hi Jouko, I have implemented this enhancement and now the plugin looks really better :D
There are several files I have touched. You can find them in the zip file attached to this ticket.
Replace them on top of the 1.4.6 plugin release, rebuild and replace the produced egg files to the ones in you trac server's plugins directory.
Then restart the server.
This is needed as I didn't increase the plugins release numbers, so installing from the Admin page will not work.
Also remember to clean your browsers cache, since part of this implementation is in the javascript code.
Let me know what you think.
Ciao, Roberto
comment:3 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Implemented in 1.4.7.
I set the severity as major, since this actually is a major problem to my test team at the moment. They do have such a slow conection to the server :( . So the good intention to ease their job with the plugin has turned into a fail as it takes too much of their time to repor the statuses one by one.
Then again this is not major to most of the users, maybe not even normal. I hope my point on the 'major' is understood, even there might be solutions to go around the problem. I ceratilny will look for those too and keep the ticket up to date.