Confirmed users
4,072
edits
QA/Sync/Test Plan/grinder tests: Difference between revisions
Jump to navigation
Jump to search
→Script use pattens
| Line 48: | Line 48: | ||
New functions can be added as new services are rolled out. A lot of potential use cases will be able to be simulated by this system. For example a dupes test could be run by syncing the same data multiple times with serperate client objects. | New functions can be added as new services are rolled out. A lot of potential use cases will be able to be simulated by this system. For example a dupes test could be run by syncing the same data multiple times with serperate client objects. | ||
=== Script use | === Script use patterns === | ||
We currently have the ability to go through the logs and see how the sync server is being used. We can generate a profile based on this and do load testing that way. In addition, we can add scenarios that model other use cases. For example: | We currently have the ability to go through the logs and see how the sync server is being used. We can generate a profile based on this and do load testing that way. In addition, we can add scenarios that model other use cases. For example: | ||
* A period with above normal registrations | * A period with above normal registrations | ||