- Open a Browser and enter the URL :http://testrail.pentaho.com/index.php?/auth/login/
- Enter your Login id and password and click on the login button.
- Dashboard Page is displayed with All Projects graph, Projects section with various versions.
- Select a Version Number.
- Overview Tab is selected by default. An activity graph, Milestones,Test Runs and a very detailed Activity list is displayed.
- Select the Test Suites & Cases tab.
- Select Master, Test cases are displayed and on the Right side the Projects are listed.
- From the Right Side select a Project.
- The test cases for that project are displayed.
- Follow the above steps and select the project to which you need to add a test case.
- On the top tool bar click on the + Add Case button.
- Add Test Case page opens with the following fields.
- Title - A title for your test case
- Section - A Project where this test case belongs to( you can change to another project if you would like to)
- Template - Exploratory Session, Test Case (Steps), Test Case (Text)
- Type - Bug Related, Functional, Helper, New Enhancement, Performance, Regression, Security, Smoke & Sanity
- Priority - Critical, High, Medium, Low
- Estimate - Duration to run the test eg 30m,1h
- References - JIRA ticket to refer to ( Add link will open a JIRA page with Create Issue page)
- Status - Draft, Approval, Active, Inactive
- Automated - Yes, No
- Preconditions - Any set up to do to run the steps
- Steps - Step Description, Expected Result (Icons for Add a step, delete a step, add an image to the Step field or expected result field)
4. Click on the ? icon to open the TestRail User Guide - to learn about the rich-text formatting.
5. Click on the Add Test Case button to save the test case to the project.
- Click on the Test Suites & Cases tab.
- From the tool bar select Filter.
- A drop down pane appears with a lot of options
- Expand the Title option
- Leave Match all of the following radio button as it it.
- Click on the Drop down near Is and select Contains option, in the field next to to it enter the title of the test case that you want to filter.
- Click on the OK button. The Filter details appears on the tool bar and the test cases that contains the text your entered earlier will be the ones that are listed.
- Select a test case to Edit.
- On the Top right side an Edit button is present
- Click on the Edit button, the test cases fields are opened in Edit mode
- Make necessary changes to the test cases, click on the green + or red - icons to add a step or delete a step
- To add an attachment to the test case, on the Right Side there is a Drop files to attach, or click to browse panel, click on it to browse an attachment from your local file system and then click on the Open button to add the attachment to the test case
- After making all the changes, click on the Save Test Case button to save the test case
- Login to TestRail
- Click on the 7.x Project or the latest version to test.
- Click on the Milestone Tab
- Choose the ‘22.214.171.124 Regression Testing’ milestone
- Click on a ‘Test Plan’
- Click on a ‘Test Set’ in the list
- The test cases to run on different versions are listed
NOTE: You must assign the Test Case to yourself FIRST!!!!, this way we don’t have multiple people running the same test at the same time
To run a ‘Test Case’
- Click on ‘Add Results’ in the top right
- Assign it to yourself
- Enter the Version (example: 126.96.36.199-294)
- Click on ‘Start’ next to Elapsed (this starts the timer)
- Go through the steps, If something fails put in the Actual results
- When complete, go to the bottom and click Add Results (This will stop the timer)
What to set for test case status while running both (Manual & Automation):
|“Passed” (Green)||All steps in a test provide the|
|“Passed – Known Issues” (Orange)||Almost all steps in a test provide the , but a step(s) has an existing documented BUG that is not resolved|
|“Blocked” (Dark Grey)||Cannot continue working on a step flow due to an issue (to be detailed later)|
|“Failed” (Red)||Test and/or step does not provide the|
|“Retest” (Yellow)||Test case that needs to be re-run due to various factors (to be detailed later)|
|“Untested” (Grey)||Test cases that have not been run|
|“Bad Test Case” (Fuchsia/Pink)||Test step(s) that are written poorly, do not provide clear , or generally vague to the person running the test case|
When to use “Failed” or “Passed-Known Issues”.
When looking up an existing JIRA use the ‘Severity’ of the issue as the determining point of which status to use.
|Mark the TR Status||Description|
|Passed|| Known issues, where the JIRA severity is
|Passed-Known Issues|| Known issues, where the JIRA severity is
|Failed|| Known Issue, where JIRA severity is
|Failed||New issue found or Possible Regression|
When entering a defect in TestRail, you only need to enter the ID, and not the URL.
Good: BACKLOG-1234, BACKLOG-12345 ( add ", " between JIRA id numbers)