Ewan defines two promotion levels, QA and Production. In future, only code that has reached the Production level will be included in external builds (i.e. those destined for clients). He has configured the security for each promotion level as followed:
| · | QA level
|
Only users in the QA group can view this level.
| · | Production level
|
Only Ewan can view this group
This will be the first time that the QA department have reviewed GP-Install as it had been tested and built by the developers themselves. To put it to the test, Ewan decides that a new build should be created for existing clients.
Ewan, as he is a member of the development group, decides to promote the latest version of the project to the QA level. Before doing so, and so that he can always go back to that version in the future, he attaches the current build number 5.0.2.57 as a Version Label to the entire project. He also defines a view, based on that version label, and makes it current in Version Manager.
He selects the GP-Install project and selects Action/Promote to 'QA' from the main menu. The promotion criteria dialog box is displayed to allow him to check the criteria to be used for this action. He reviews the information and presses the OK button to promote all the files at version 5.0.2.57 to the QA promotion level. He then informs the QA department that they can now begin testing GP-Install.
Christine is a member of the QA department and is asked to test GP-Install. She starts up Version Manager and defines a view based on the QA promotion level. She selects that view to make it current and does a Get on the GP-Install project to get a local copy of all the files at the QA promotion level. She does a build using these files and begins testing.
Christine's testing uncovers quite a few User Interface problems, which must be fixed before the product is re-released. She compiles the list of problems using TCTracker and informs the development team of their existence.
Joanne is tasked with fixing the problems and begins work on the changes. The changes take a couple of days and during that time Christine uncovers more problems. Alan is called in to help with the changes. As Alan and Joanne make the fixes, they promote the individual, fixed files, to the QA promotion level by selecting them in Version Manager and selecting Action/Promote to 'QA' from the main menu.
After a further couple of days, Alan and Joanne are happy they have fixed all reported problems and inform Ewan that this is the case. Ewan tells the QA department that they can re-test the files at the QA promotion level.
Christine opens Version Manager, selects the view based on the QA promotion level and refreshes the GP-Install project. She rebuilds the project and carries out more tests. Joanne and Alan have been working very hard and Christine's testing confirms that the problems she reported have been fixed.
Christine's testing does not uncover any more problems and she is now happy that the code is now in a fit state to be released to the clients. She starts up Version Manager and makes sure that the view she defined, based on the QA promotion level, is current. She right clicks on the GP-Install project and selects Promote to 'Production' from the popup menu. The promotion criteria dialog box is displayed and she presses the OK button to promote the files to production. She informs Ewan that this has been done.
Ewan starts Version Manager, defines a new view based on the Production promotion level, and makes it current. He knows that all files at this level have been passed by QA and are deemed ready for production. He does a refresh to get the revisions of the files that make up the Production level, and does a build. The new release of GP-Install is packaged and sent to the existing clients.
© 1995-2018 MCN Software