In the following article, we will learn how to create your first Native Android Application Test Case and to execute the same on Testsigma Labs(containing 100+ Real mobile devices to choose from).
The Application under Test(AUT) is Wikipedia Android App(Latest version as of writing this article).
Create and Run your first Android Native Application Test Case on Testsigma Labs
Please follow the below steps to create and run your Android Native Application Test Case.
1. Create a Project, Application and Version
From Testsigma Dashboard page, click on the Create New button and then click on Project to create a new Project as shown below.
Enter the required details: Project Name, Application Name, Version Name and Application Type.
Note: Enable the checkboxes if you need multi-Application and multi-Version tracking in single Project. You may leave it unchecked if you are not sure.
Clicking on Create button creates the Project, Application and Version in a single Step and takes you to the Test Cases page.
2. Import the UI Identifiers
UI Identifiers in Testsigma are used to locate the Elements on your Application Screen/Page such as buttons, fields e.t.c.
For this guide, we have already created the UI Identifiers required in this Test Case for you in importable format. Let us import the UI Identifiers now.
Download the attached "fieldDefinition.xls" file at the bottom of this page.
Click on UI Identifiers link on the left context menu to go to UI Identifiers page. Click on Import button to import the UI identifiers as shown below:
You can also get to UI Identifiers page from Test Development > UI Identifiers
In this case, we have already created the UI Identifier for you. Please check the below article to know how to create UI Identifiers for your Android Native Test Cases.
3. Create the Test Case.
Click on Test Cases link on left context menu once again to go back to the Test Cases page. Click on + Test Case to create a Test Case as shown below:
Enter a Test Case name and click on Create button to Create the Test Case. We will be taken to Test Case details page.
4. Add First Test Step
The first step is to Launch the Wikipedia App.
Type 'Launch' in Action Text box and select 'Launch App' from suggested NLP Statements. Now, click on Create & Continue to add the Step and continue onto adding next Test Step.
5. Add the second Test Step.
The second step is to tap on Skip button in the Wikipedia Loading page as shown below:
For adding the second Test Step to tap on the Skip button, do the following:
Type 'tap' in Action text box and select 'Tap on ui identifier' from suggested NLP Statements.
Double click on ui identifier, press Backspace key to delete it and select 'skip_onboarding' from the suggested ui identifiers list.
Remember we had already imported the UI Identifiers and that is the reason the UI Identifiers are shown in suggestion. We can also create a UI Identifier by entering it's name. We will learn that in another article.
6. Add the remaining Test Steps
We have added the first two steps. We need to add step 3 to 6 to the Test Case.
#1. Launch Application #2. Tap on skip_onboarding #3. Tap on sync_readinglist_gotit #4. Tap on menu #5. Tap on hide card #6. Tap on search
Follow the same step as shown above and simply select the corresponding UI Identifier from the suggestions.
7. Upload the Wikipedia App(AUT) for testing
Download the attached "Wikipedia_v2.7.269.apk" file at the bottom of this page.
Click on Uploads link from left context menu to go to Uploads page. You can also get to this page from Dashboard by going through Test Development > Uploads
Click on the Choose File button and select it from the File explorer where it was downloaded.
Then, click on Upload button on Uploads page and upload it as shown below:
8. Create and Run the Execution
Go back to the Test Cases page and click on Run button on top right corner. Modify the required details and leave the rest as it is.
Run the Test by clicking on Create and Run button.
Once the execution is started, it will take some time for it to complete and it will be in queued status until completion. After the execution is complete, the Test Result status will change to Passed, Failed, Aborted, or Stopped as per the execution outcome.
Happy Test Automation!