From: Webber, Steven SW
Sent: 13 January 2009 10:03 AM
Subject: RE: CI + QC + QTP
Our current thinking is:
Unit tests are executed with each build.
Integration tests, written by developers, are executed with each deployment to INT. (Nightly/after a successful build)
QTP scripts are executed only when the build is promoted to UAT. (Bi-weekly? End of Sprint..?)
Not sure how much of this can be fed back to CI?
From: Van Der Merwe, Ben B
Sent: 13 January 2009 09:49 AM
To: de Vleeschauwer, Camiel C; Venter, Carl c; Webber, Steven SW; craig;
Phale, Mafatshe M; Mase, Luvuyo L
Cc: charles; Frazer, Shirley
Subject: FW: CI + QC + QTP
If some of the acceptance / 'smoke' tests have been automated/mechanised
(with QTP scripts) it makes sense to execute them with each (nightly)
build that is deployed to UAT and feed the results back to the CI tool.
In terms of the incremental / hourly builds it makes sense to execute
unit tests and unit integration tests as part of the incremental builds
and to feed the results back to the CI tool.
Maybe we can work towards some goals in both of these areas? Who else
need to be involved?
From: Craig McKenzie
Sent: 13 January 2009 08:00 AM
To: Van Der Merwe, Ben B; Phale, Mafatshe M
Subject: CI + QC + QTP
I'd like to know if there is the possibility that the QTP results could
be wanted in the CI tool (or if the CI tool should possibly execute the
Technical Testing Consultant
Micro to Mainframe