Trac Hacks - Plugins Macros etc.: Ticket #3282: tracforms for test cases?https://trac-hacks.org/ticket/3282
<p>
could this be used to plan tests and execute test cases multiple times, like e.g. <a class="wiki" href="https://trac-hacks.org/wiki/TestCaseManagementPlugin">TestCaseManagementPlugin</a> supports it?
</p>
en-usTrac Hacks - Plugins Macros etc.https://trac-hacks.org/chrome/hacks/png/trachacks_banner.pnghttps://trac-hacks.org/ticket/3282
Trac 1.2.2anonymousMon, 30 Jun 2008 17:05:58 GMTstatus, owner changedhttps://trac-hacks.org/ticket/3282#comment:1
https://trac-hacks.org/ticket/3282#comment:1
<ul>
<li><strong>status</strong>
changed from <em>new</em> to <em>assigned</em>
</li>
<li><strong>owner</strong>
changed from <em>Rich Harkins</em> to <em>anonymous</em>
</li>
</ul>
<p>
I'm certainly know of no reason why it couldn't, given that TracForms included in tickets will bind to the ticket for context as opposed to where the form's body is located. However, that particular use case isn't something that TracForm is specifically aiming at. Let's think out a simplified example, supposing a two-test suite.
</p>
<p>
In the wiki page TestCases/TestClose:
</p>
<pre class="wiki">== Description ==
Test the close button works.
== Steps ==
1. Open the application
1. Click the close button (X) in the upper-right.
== Success Criteria ==
1. The window disappears and the associated entry disappears from the task bar.
</pre><p>
In the wiki page TestCases/TestMinimize:
</p>
<pre class="wiki">== Description ==
Test the minimize button works.
== Steps ==
1. Open the application
1. Click the minimize button (_) in the upper-right
== Success Criteria ==
1. The window disappears but the application label stays in the task bar.
</pre><p>
Now, let's bind these into a test suite on the wiki page TestSuites/Windowing:
</p>
<pre class="wiki">
{{{
#!TracForm
|| || '''Test Case''' || '''Notes''' ||
|| [tf:close] || [wiki:TestCases/TestClose] || [tf.input:notes/close]
|| [tf:minimize] || [wiki:TestCases/TestMinimize] || [tf.input:notes/minimize]
}}}
</pre><p>
Now, all that is needed to stick this in a task is to simply include it (if you have the <a class="wiki" href="https://trac-hacks.org/wiki/IncludeMacro">IncludeMacro</a> or some other equivilent). Create a new issue and in the description add:
</p>
<p>
[Include(TestSuites/Windowing)]
</p>
<p>
At this point, the task itself should now have the checklist built in. Unfortunately, there is no way to keep the workflow from proceeding until the checkboxes are complete, but that part is definitely planned.
</p>
<p>
I don't know if the above covers what you were looking for. I've played with the plugin you mentioned (<a class="wiki" href="https://trac-hacks.org/wiki/TestCaseManagementPlugin">TestCaseManagementPlugin</a>), but haven't really done anything with it. I suspect that my own processes will likely use TracForm, partially because I'm working on it and want to advance that direction, but also because of the flexibility that general purpose forms could provide.
</p>
<p>
If the description above meets your needs, please resolve this ticket.
</p>
<p>
Thanks!
</p>
TicketRich HarkinsMon, 30 Jun 2008 17:10:43 GMTowner, status changedhttps://trac-hacks.org/ticket/3282#comment:2
https://trac-hacks.org/ticket/3282#comment:2
<ul>
<li><strong>owner</strong>
changed from <em>anonymous</em> to <em>Rich Harkins</em>
</li>
<li><strong>status</strong>
changed from <em>assigned</em> to <em>new</em>
</li>
</ul>
TicketRyan J OllosTue, 09 Jun 2009 05:33:38 GMTcc changedhttps://trac-hacks.org/ticket/3282#comment:3
https://trac-hacks.org/ticket/3282#comment:3
<ul>
<li><strong>cc</strong>
<em>Ryan J Ollos</em> added; <em>anonymous</em> removed
</li>
</ul>
Ticket