Once the Integrated Test is completed, the application must be sent to Functional Test. The application tested by the Functional Test team must be exactly the same as that used in the Integrated Test process.
To move the application to Functional Test, the Integrated Test team leader creates a new version of the application in GXserver (it is created based on the Integrated Test version, because the same objects included in the Integrated Test will be tested in Functional Test).
Next, a Create KB from Server is performed. Selecting the All Versions option, the application is generated, compiled and deployed to begin the Functional Test.
If bugs that must be fixed are found during the Functional Test process, the same steps should be followed as in the Integrated Test.
The Integrated Test team leader has to perform the steps below:
-
Update the Main Development Version in his Local KB (performing an Update to obtain the latest changes that have been made). Objects that were created by the development team but don’t need to be moved to Test at the moment can be sent in this step.
-
Compare the Main Development Version with the Integrated Test Version to see what changes have been made (the objects that have been changed) from the dialog box to compare versions.
-
Decide which objects must be sent to the Integrated Test Version, and generate an xpz with those objects.
-
Switch to the Integrated Test Version, import new objects.
-
Commit those objects on GeneXus Server to update the Integrated Test Version.
-
Import the same objects to the Functional Test version, to be updated locally.
-
Perform a Commit of those changes to the Functional Test version, to send all the changes to GXserver and update all versions on GXserver.
Just as it happens in Integrated Test, errors may be found that need to be fixed in the Local KB as soon as possible. In this case, the steps indicated in this page should be followed.
If there are more Test teams involved, these steps are repeated with each one of the Test teams.