Process
Description
Testing is necessary in any product type, below we are focusing on a digital product, however, you should adapt this to the type of product you are producing. It is extremely important to make sure that the product you are putting on the market meets certain quality levels, first for consumer safety and second, for customer satisfaction. Make sure you meet certain satisfactions based on your industry and brand value, however, do not get so caught up with quality that you end up hindering the release and success of your product, get your product to market with the minimal quality and improve rapidly. Testing is necessary in any product type, below we are focusing on a digital product, however, you should adapt this to the type of product you are producing. It is extremely important to make sure that the product you are putting on the market meets certain quality levels, first for consumer safety and second, for customer satisfaction. Make sure you meet certain satisfactions based on your industry and brand value, however, do not get so caught up with quality that you end up hindering the release and success of your product, get your product to market with the minimal quality and improve rapidly. Expected Outcome By now we want all parties involved to have a better picture of the problem we want to solve, for who we are solving it, and all relevant information. Links & Resources Details & Status Assigned To Due Requirements Time Frame Documents Status Tasks Person Date
2 Weeks File New
Expected Outcome
By now we want all parties involved to have a better picture of the problem we want to solve, for who we are solving it, and all relevant information.
Details & Status
| Assigned To | Due |
|---|---|
| Requirements | |
| Time Frame | 2 Weeks |
| Documents | |
| Status |
Tasks
- Person
Results Feedback Be sure to listen to your customers and be open to criticisms.
Testing & Release Process
Testing process
There will be two types of tests: automated and manual. The automated tests will be made at the same time we are developing the code. The manual tests will take place when the code is finished. There are many different types of devices with different views sizes. As this is only a prototype, we can focus on popular devices; however, in the Final Product, we will need a lot more testing. For these manual tests, there will be many steps to this process: Internal Alpha Alpha starts off extremely unstable and filled with bugs and it gets worked out through the process. Internal Alpha is meant for employees only. We all use the app and report back about the bugs we find. Private alpha Once the app is a little more stable we push it to the next level; here there are friends of friends, paid testers and perhaps yourself and some friends. Limited Alpha Here it starts to get exciting. It is not officially released but we open a channel where users can sign up to use the app with the understanding that it is not completed and they may encounter some problems. Internal Beta Once we feel it is up to the task, we release an internal beta. This means 5 to 10 of our employees will receive the stable version. If they don’t encounter any issues (and they shouldn't) then it’s off to the next step. Private Beta Once again this is for a group of testers we pay, you and your friends, and other users we trust to provide valuable feedback. Limited Beta We allow a limited number of users to join. Public Beta Anyone can join but we can set a limit. A useful amount would be 1000 users. Final Release It is off to the world, anyone can snag your app!
There will be two types of tests: automated and manual. The automated tests will be made at the same time we are developing the code. The manual tests will take place when the code is finished. There are many different types of devices with different views sizes. As this is only a prototype, we can focus on popular devices; however, in the Final Product, we will need a lot more testing. For these manual tests, there will be many steps to this process: Channels & Progressions There are four release channels: Internal, limited, private and public. Adicanaly there are three progressions Alpha, beta and production,
-
Alpha
Alpha starts off extremely unstable and filled with bugs and it gets worked out through the process. Internal Alpha is meant for employees only. We all use the app and report back about the bugs we find.
-
Internal
-
Private
Once the app is a little more stable we push it to the next level; here there are friends of friends, paid testers and perhaps yourself and some friends.
-
Limited
Here it starts to get exciting. It is not officially released but we open a channel where users can sign up to use the app with the understanding that it is not completed and they may encounter some problems.
-
-
Beta
-
Internal Once we feel it is up to the task, we release an internal beta. This means 5 to 10 of our employees will receive the stable version. If they don’t encounter any issues (and they shouldn't) then it’s off to the next step.
-
Private
Once again this is for a group of testers we pay, you and your friends, and other users we trust to provide valuable feedback.
-
Limited
We allow a limited number of users to join.
-
Public
Anyone can join but we can set a limit. A useful amount would be 1000 users.
-
-
Production
It is off to the world, anyone can snag your app!
We need to remind you that until Private Alpha all testers need to sign an NDA so your intellectual property is protected.
Testing Tools & Setup
To setup testing see the Release Tools
Feedback
Be sure to listen to your customers and be open to criticisms.