On May 29, 3:47 pm, david bonnin <[email protected]> wrote: > none want to share his experience in documentation? > > [email protected] a écrit : > > > For my project, we have to descride tests, so i look for tests management > > intergrated with trac. > > Can you share your experience on tests docs management with trac? > > My project is for industry that want tests-documents > > > 1-How do you manage tests associated to tickets? > > today: i manual attach a file "ticket_xx.doc" > > It isn't a specific field, and without any control on the > > name(ticket_34.doc must be attach with ticket#34). > > In a perfect world, the test description must be a "web form". > > > 2-How manage plan of validation in trac? > > or do you know plugin that do it? > > A ticket can be link to a test in the "test plan" > > After find a bug, a test in the test plan can be modify, so link it to > > ticket. > > > test-plan: > > project01: GUI --> test01_start_form.doc > > test02_identification form.doc > > test03_control panel.doc > > test04_action form > > test05_parameters form > > NETWORK --> test06_openning.doc > > test07_closing.doc > > PROCESS --> test10_process01.doc > > test11_process02.doc > > > Do you understand what i try to say by "tests plan" or "plan of validation"?
Not sure what you are after, but have you checked the TestCaseManagmentPlugin or the QATracker plugin? Sounds a lot like you are after. Of course they don't map to msword documents like your example. Personally, I have a custom wiki filed (howtoverify) that is expected to be populated with [wiki:Tests/Verification/NNN] where NNN is the ticket number I have a template which includes a link back to the ticket by #NNN and has, in this case, how to verify section, as well as a section for "verification" results to be filled in later. My workflow has a "verification" step to close a ticket. to verify, you click through the link, and fill in the results section. my field is also required to be filled in when "resolving" a ticket by the TicketValidatorPlugin so an author can't close a ticket withough putting somethign in how to verify. The down side here is, NNN has to be manually edited after creating the ticket since the ticket # isn't know yet. Same thing on the wiki page for the Verification tests page. I am starting to look into how to make a macro that will populate that information with the resource ID value, which for this will be the ticket # in the ticket, and the matching "page id" on this wiki page, which is laid out specifically to be the ticket number only(I suspect I'll have to split of "Tests/ Verifications/" in this case. The same can be extended for Validation tests. I have the same setup for author tests. I then have a top level link to wiki:Tests with titleIndexes for Verification and AuthorTests. Verification, and Authortests have a titleIndex as well for 1, 2....500 What I get for this? When the project is done, I can dump everthing from wiki/Tests/Verificaiton/* with the WikiPrint plugin, and dump the pages to a PDF book, for later printing/archiving. whew. Another option would of been to create a ticket type called validation, with a wiki fomatted text area with "how to verify", and require blocking to have a value with TicketValidator. And a custom resolution of Passed. This would give you a Blocking validation ticket, which you would have to validate before "closing" the original ticket. In my case, I also have a FeatureTicket type, which is blocked by all the sub tickets. All my subTickets have a verification workflow step, so the FeatureBranch itself is blocked until all the tickets in the feature have been intergrated and verified. The feature is then closed with "merged" status. The featureBranch is also given a milestone for tracking purposes. Finally I have a ticket type called Test, which is blocked by the FeatureTicket mentioned above. This ticket references a Validation Suite for the feature, that our test group builds, based on requirements docs, and often the "how to verify" sections of the little tickets. It is the last ticket in a feature branch to actually close, closing the feature. It's in it's infancy, and needs tweaking, but that's the general approach we use. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
