Still doing manual tests?
When performing tests manually, users are in one of these situations:
- They only test a few test cases chosen randomly
- They only test those test cases that they think have more chances to fail
- They do exhaustive manual testing.
If your case is one of the two first ones, there are many chances that the CPEs deployed will cause you trouble in the future. A very simple error in TR-069 like a wrong implementation of a writable parameter, can cause that you cannot perform a remote configuration when a user calls your call center for help; a wrong implementation in an RPC method could cause that a remote configuration is performed partially and leaves the CPE in a state that cannot be accessed again until the user performs a manual reboot; the CPE can lose connection with the ACS, etc. There are many situation that you want to avoid, and that you could, if you tested TR-069 throughly.
If your case is the third one, and you are performing exhaustive manual testing, you are probably facing at least one, or many of the following problems:
- Your time to market is much longer than what it could be.
- Your technicians’ job is repetitive and time consuming. They get bored in their jobs, and you have many chances to suffer too much stuff turnover, which results in continusly loss of know how.
- Your technicians are humans, no matter how good they are they make mistakes sometimes,
- When testing manually, you cannot guarantee that the same test cases have been always perfommed under the same conditions in different testing itterations, so it is possible that they have considered a test case to pass and the same tets to fail because the initial conditions were different.
More info about dBm069-ATP069 |