Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We need to create the Test issue first and fill out the Gherkin statements later on in the Test issue screen.

Image Modified  Image Modified  



After the Test is created it will impact the coverage of related "requirement", if any.

The coverage and the test results can be tracked in the "requirement" side (e.g. user story). In this case, you may see that coverage changed from being UNCOVERED to NOTRUN (i.e. covered and with at least one test not run).


Image Modified


Additional tests could be created, eventually linked to the same Story or linked to another one (e.g. logout).

...

Code Block
titlefeatures/1_COMXT-19225.feature
collapsetrue
@REQ_XT-225
Feature: Login feature

	@TEST_XT-226
	Scenario: Test Login feature
		Scenario Outline: As a user, I can log into the secure area
				Given I am on the login page
				When I login with <username> and <password>
				Then I should see a flash message saying <message>
				
					Examples:
						| username | password             | message                        |
						| tomsmith | SuperSecretPassword! | You logged into a secure area! |
						| foobar   | barfoo               | Your username is invalid.      |

...

Results are reflected on the covered item (e.g. Story). On its issue screen, coverage now shows that the item is NOK based on the latest testing results, that can also be tracked within the Test Coverage panel bellow. 

Image Modified
  

Using Git or other VCS as master

...