Confirmed users
487
edits
TestEngineering/Services/LoopServerLoadTesting: Difference between revisions
Jump to navigation
Jump to search
m
TestEngineering/Services/LoopServerLoadTesting (view source)
Revision as of 17:30, 12 May 2015
, 12 May 2015Add section for e2e test
Rpappalardo (talk | contribs) m (Outline updates) |
Rpappalardo (talk | contribs) m (Add section for e2e test) |
||
| Line 444: | Line 444: | ||
* The Services cluster is here: | * The Services cluster is here: | ||
** http://loads.services.mozilla.com | ** http://loads.services.mozilla.com | ||
= End-2-End Testing = | |||
End-2-end (or: "e2e") testing is a comprehensive means of testing back end services. An e2e test is essentially a test where you perform the same actions a user would in such a way as to ensure that the client is correctly consuming all backend services. This kind of verification should ideally be performed after STAGE verification and loadtesting and just prior to PRODUCTION deployment. Performing an e2e test during PRODUCTION deployments also helps to witness firsthand what the customer will see just prior and just following DNS switch on a production release. | |||
== Loop-Server | |||
TBD | |||
== Loop-client | |||
TBD | |||
== msisdn-gateway | |||
TBD | |||
= Known Bugs, Issues, and Tasks = | = Known Bugs, Issues, and Tasks = | ||