QA/Sync/Test Plan/grinder tests: Difference between revisions

QA/Sync/Test Plan/grinder tests (view source)

479 bytes removed , 25 May 2011

89

edits

@@ Line 3: / Line 3: @@
 ;We are trying to accomplish the following goals:
-*Create a continuous baseline testing framework (tied to hudson)
+*Create a continuous baseline testing framework (tied to Jenkins)
 *Be able to answer questions about current and future growth.
-** What types of services can we support now and what changes can we support in the future?
+** How can our app fail now?
+** What types of services can we support in the future?
-;We are trying to answer the following questions:
-* How does the app fail under high load conditions? How does it fail?
-** From a large data input?
-** From a lot of connections?
-* Which functions and potential use cases create a particularly high amount of load?
-** High amounts of registration? (and corresponding initial sync?)
-** Lots of empty requests? (as generated by instant sync?)
-* Are any functions effected sooner by high load?
-* How do these services scale?
 == Test Cases ==