This is our first article on the rare topic – Device Testing.
In this Tutorial, we will help the Engineers to learn the different aspects and approaches of testing mobile devices.
Also, you will get familiar with many useful tools for performing Device Testing on different mobile devices.
And, you can enable yourself for up-to-date test planning for mobile device testing and any mobile device product launches.
So, let’s get started.
What is Device Testing?
To start with this Device Testing Tutorial, we need to ask the below few questions first:
How Xiaomi is testing different Mobile Products (i.e. The Mobile Devices that has to be launched in different countries)?
How OnePlus is launching their Flagship phones?
How Samsung, Motorola or any Phone Oppo is getting launched across the Globe?
Who is the person responsible to make this products live?
The answer for all the above questions is “Device Testing”.
Every OEM company (Original Equipment Manufacturer) have their test lab and have a test team set-up who will be responsible for the below things which can be part of Device Testing:
- Network Testing
- OTA (Over The Air) Testing
- Top Apps Testing
- GMS (Google Messaging Services) Testing
- CTS (Compatibility Test Suite) Testing
- Field Testing
- Factory Testing
I will explain to you all the above terms in the upcoming articles and help you in getting hands-on the same along with the tools to be used for different purposes.
So, I will start with an example.
Suppose Xiaomi company is going to launch a new model of MI devices.
How the testing (as a device tester) will be performed in this case?
For any device to be launched, Company decides their phase of launching prototype and this prototype is called EVT (Engineering Verification Testing) .
EVT is a test performed on prototype product at Alpha phase.
The goal is to verify if the products meet product specification and if there are any critical problems that are blocking the product from going into the next phase.
Once this Prototype is finalized, the company will launch another version of the same phone i.e. DVT (Design Verification Testing).
After prototyping, the product is moved to the next phase of design cycle: Design Refinement.
Engineers revise and improve the design to meet performance and design requirements and specifications.
Design Verification Testing (DVT) is specific product verification tests performed to deliver objective, comprehensive testing verifying the following:
- All products specifications
- Interface Standards
- OEM Requirements
- Diagnostic Commands
On this phase completes, company is going to launch their different version of the same phone. i.e. PVT (Product Verification Testing) / MVT (Manufacturing Verification Testing).
As you can guess, this test is performed at the production phase and before the product goes to mass production to sell. The goal is to make sure that the main features work by performing the wide and shallow tests. i.e. No deep tests are needed at this phase.
In the next section, I will explain to you – ‘The kind of testing that need to be performed on Devices as part of DVT, EVT and PVT’.
> To learn more about WebDriverIO, continue to the next post (Click on Next Post link below)
> Check complete WebDriverIO Tutorial Contents here (Click here)
Please leave your questions/comments/feedback below.
Happy Learning 🙂
On a mission to contribute to the Software Testing Community in all possible ways.