Note: The video will be updated soon.
There are two ways to create a test case in the platform:
- Creating a new test case in the platform
- Importing test cases from a CSV file
In this course, we will consider creating a test case inside the platform. See the next course for the import option.
To begin, choose a product from the Product Picker and open the Test Case Management tab. From the All Test Cases tab click the plus button to bring up the creation page.
Test Case Creation Form - Settings
Name
Keep the name brief yet descriptive.
Description
Optional description of the test case. Provide a short clear description, indicating the areas of the app that the test case covers. You can format the text in the field if necessary, like changing the text style to Bold, Italics, Underline, highlighting, using ordered and unordered lists, etc.
Test Suite
If you already have test suites defined, choose one or more appropriate test suites for the test case.
Priority
The priority ranks the importance of the test case.
External ID
External ID can be used to avoid confusion if there are more than one identical test case names or if you have unique identifiers for the test cases.
Reference
If needed, map the test case to a corresponding test case in your Bug Tracking System. E.g.:
- Label: Jira
- Value: https://myutest.jira.com/browse/FLO-30613
Automation Candidate
Adds the test case to the list of available test cases for automation.
Next Page
Once you're done, click the Next: Add Steps button.
Test Case Creation Form - Adding Steps
Next you will need to add test case instructions and steps.
Preconditions
You can specify any preconditions that need to be prepared in order to start executing the test case. You can format the text in the field if necessary, like changing the text style to Bold, Italics, Underline, highlighting, using ordered and unordered lists, etc.
Test Case Attachments
If necessary, add some attachments to provide the tester with more detailed instructions.
Steps
Name - Provide a short name for the test case step.
Instructions - Actions that need to be carried out in this step. You can format the field if necessary.
Step attachments - Attachments that can be provided on a step in addition to the step instructions.
Expected Result - Explain what the tester should see or experience when the instructions are performed. You can format the field if necessary.
- If the tester correctly encounters the expected result, then the test case step will Pass.
- If the tester encounters an error or some other outcome, they’ll report this step as having Failed.
Branching - Can be used to work with different scenarios a tester may experience and collect different data points based on their responses.
- Branching works with Radio question types and expected results. A result can branch into other questions, steps, required attachment modules or the end of the test case.
- When a test case has branching, testers will not be able to see previews for that test case, and they will not be able to see the next step or question unless they complete the current step.
Step Modules
You can add two modules to a test case step: Attachments and Question.
The Attachment module is for requiring attachments from the tester.
- The Attachment Title won’t be shown to the testers, it’s only for reporting purposes
- Write Attachment Instructions and specify how many attachments are required
The Question module is for asking survey questions that capture contextual information about the testing being performed.
The question type can be Checkbox, Date/Time, Free Text or Radio.
- Note that you can use branching for the Radio question type, only this type has branching.
- Also you can pass or fail the step depending on the answer to a question.
The Question module can be used to:
- Collect some quick feedback on your product or a new feature of the product
- Collect some extra information about the testing the testers did
- Replace various spreadsheets or external surveys
Available Actions on Steps
- Click “Add a New Step” to add a step to the test case.
- Rearrange steps by dragging the step cards.
- Remove a step by clicking the trash icon in the top right corner of the step.
- Clone a step, add attachments module or add a question module to a step from the context menu.
Saving the Test Case
Once you’re done drafting the test case, you can save it by clicking “Save & Publish” or “Save as Draft”.
Note: After creating a new test case, you should contact your Applause management team to discuss when and where you’d like it to be utilized during testing.
Utilizing Test Cases for Data Collection
You are able to utilize the Applause testing community to do much more than simply running exploratory and structured testing. Surveys are a great way to enhance the types of data you can collect during testing.
Test Case Surveys allow you to present the testers with fully customizable questions of different types - single / multi select, date-time, numerical and free text. This ability may be used for several use cases, including:
- Surveying the testers on their opinions about the tested product
- Collecting customized structured data as part of the test case execution
- Timestamping different actions executed as part of the test case
Setting Up Survey Questions
Survey questions are currently set by internal-only tools. Please contact your Applause team in case you see a need for utilizing survey questions.
Viewing Survey Questions
You may view the survey questions from the Applause Platform.
To view the survey questions:
- Log in to the Applause platform.
- Select a product.
- Navigate to the Test Case Management tab.
- While on the All Test Cases tab, locate the test case that contains survey questions.
- Click on the test case name to see its details.
Viewing Survey Question Results
Test cases that are based off of survey questions are generally not expected to get a “pass / fail” result. Rather, such test cases will be marked as “completed” once all questions are answered. The answers are available to view and export like the “regular” test cases.