Changes between Version 4 and Version 5 of TicketTestsLifeCycle

Timestamp:

Feb 13, 2014, 1:51:24 PM (9 years ago)

Author:

Piotrek Koszuliński

Comment:

--

TicketTestsLifeCycle

@@ -13 +13 @@
   b. Other resolutions: {{{pending}}}, {{{invalid}}}, {{{duplicate}}}, {{{wontfix}}}, and {{{worksforme}}}. Stop here. Feedback may be provided by the reporter later.
  4. Ticket Tests created:
-  a. A dedicated test branch is created for the ticket. All added and changed tests will end up in that branch. The branch name pattern is {{{t/<Ticket Number>}}}.
+  a. A dedicated test branch is created for the ticket. All added and changed tests will end up in that branch. The branch name pattern is `t/<Ticket Number>`.
   b. Ticket tests must reflect the exact steps to reproduce the ticket issue, not tests for the root of the problem. Design tests may be created on very rare cases (usually when reporting API issues).
   c. It may happen that it is not possible to create automated tests for some tickets. In that case a manual test is required.
@@ -20 +20 @@
  5. Analysis phase. (Status {{{accepted}}})
   a. New tests could appear in this phase -- either ticket tests or design tests. All of them must end up in the ticket test branch.
- 6. A patch is provided:
+ 6. A patch is provided in `t/<TicketNumber>` branch:
   a. All new tests must PASS with it.
   b. Status: {{{review}}}.