Testrail.pptx

TESTRAIL How to guide Version 04/23 Table of Content Click on hyperlink to access content 1. Overview Introduction 2. Test Runs & Results Main Page Elements in the Main Page • Test Case Information • Sections 3. Testrail Result Input Overview • Different Options How to Add Test Results (2 slide...

TESTRAIL How to guide Version 04/23 Table of Content Click on hyperlink to access content 1. Overview Introduction 2. Test Runs & Results Main Page Elements in the Main Page • Test Case Information • Sections 3. Testrail Result Input Overview • Different Options How to Add Test Results (2 slides) 1. Overview - Introduction TestRail is a test case management tool, or End-toEnd test management tool. The website works the same way as our internal checklists. The client, the Lead along with the testers know which areas should be tested in-game and which ones have already been tested. The TestRail link is provided in the Project Info, along with the usernames and passwords. 2. Test Runs & Results – Main Page Once you have logged in, TestRail will display the test run overview page, which is the progression you have made in terms of game/app checking. LQA - Test runs are the individual runs testers proceed through for all assigned languages. 2. Elements in the Main Page Run Overview The Run Overview displays the overall testing progression and the details on the pie. Underneath, you can see the Section, i.e., which part of the game/app you are currently checking. At the bottom, you can see the items or the test cases which need to be checked. The tester should make note of the priorities and the status of each item. Sectio n Test Cases 2. Sections A test run is split into sections, which represent major areas of the game/app. These sections are split into subsections. The individual cases are found in these subsections. You can use the right part of the Test Runs & Results pages as shortcuts to get to specific test cases in a particular area of the game/app. Sectio ns 2. Test Case Information You can also make the information about a test case appear on-screen when clicking on an item. New pieces of information appear: • The expected result tab includes all the information needed to check the item as a pass. • The results & comments tab shows the status of the items with some comments written by the tester • The history & context tab displays the date and time when the status item was last modified. • The defects tab mentions Test case information 3. Testrail Result Input - Overview It is important that testers keep each section of Testrail up to date as they go through the game/app. Each time you test an area of the game/app, you need to set the related status. By clicking on the button below Status, a drop-down menu appears with different options. 3. Different options Here are the different statuses you could choose for testing: • • • • • • • Untested: the case should be checked. Passed: the case passes requirements and displays no issues. Blocked: the case could not be checked by a blocking issue. Retest: the case has been tested but needs to be checked again. Failed: the case displays an issue or a bug. N/A: the case is not applicable for testing. Not ready: the case is not ready for testing in the current build. 3. How To Input Test Results You can add a result for a test case in two ways: • either by changing the test case Status • or by selecting "Add Result" (from the test case fullscreen view or from the bottom of the test case description). Option 1: Change the Test case Status By clicking on the Untested button, you can change the status of the item to make it match with one of the options in the drop-down list. To open the full screen view for a test case, simply click on the test case description or the case ID number. Option 2: Select Add Result Changing the status or selecting "Add Result" will trigger a window pop-up. 3. How To Input Test Results By selecting the corresponding status, the site will open a pop-up window that you will have to fill in. From here: 1. Confirm the "Status" from the drop-down menu again. 2. Add a "Comment" below to explain the reason for your decision. 3. Ensure the build number is entered into the "Version" box if required. 4. If the issue is Blocked or Failed, then please ensure a bug number is entered into the "Defects" box. 5. Click on the Add Result button. Note: the other buttons are not used unless specified and media is not usually required. THANK YOU We want to keep this guide up to date and relevant for all departments. Want to add or edit some information? Want to remove outdated information? Send an email to [email protected] with the subject: How to guide – Suggestion – [HowtoguideName]