Identity/DDT Smoke Test: Difference between revisions

Identity/DDT Smoke Test (view source)

297 bytes removed , 8 June 2012

Confirmed users

134

edits

@@ Line 5: / Line 5: @@
 As BrowserID grows and the product becomes increasingly complex, it is a difficult task to introduce new features without also introducing bugs.  To help reduce the number of bugs that make it to prod as well as to ease some of the pain on our own QA team, we are introducing a WWE move - the DDT.  DDT (developer driven testing) is like jumping off the top rope to smash bugs before they have a chance to cause pain.
-QA has a well defined set of tests they perform before qualifying any release as "ready for production."  We are going to use the Sanity/Acceptance/Smoke and Support for Primaries portions of their tests as the basis for DDT.  Functional and UI tests can also be run to ensure maximal flow coverage.  If each developer/contributor is able to run through the tests on a couple of desktop browsers and a couple of mobile browsers, we should be able to completely cover all A-Grade browsers.
+QA has a well defined set of tests they perform before qualifying any release as "ready for production."  We are going to use a very slimmed down version of the Sanity/Acceptance/Smoke tests.
 Tests should be performed against both dev and staging.  123done.org will be the RP of choice once it is set up to handle all environments.  123done.org currently only supports staging.  Until 123done.org is ready, testing will take place using myfavoritebeer.org as the RP.