When it is decided that the application should be sent to the Integrated Test team (so as to test the application in an integrated manner), the Development Integrated Test Version has to be updated (Consolidated KB).
This version can be created when starting the development work, and left empty until the decision is made to send the application to Test. In that moment, the objects that will be sent to Integrated Test will be sent to the version.
This KB is called Integrated Development Test, because tests are made on the application using real data. In addition, other products that the Development Team hasn't installed on their Local KBs can be installed on this version, such as GXportal or third party products. For this reason, the Integrated Test of all products should be made.
This KB is administered by the Integrated Test team leader, who decides which changes made by the development team will go to Test, as not all the changes made by the development team are sent to Test.
That’s because there may be parts of the application that haven’t been completed and don’t have to be sent to Test yet. The developers continue to send these changes to the Main Development Version, but right now they don't need to be tested in an integrated manner with the rest of the application.
For example: the development team is working on these modules: Purchases, Stock and Orders. The Purchases module has already been completed, and this is the only module that the development team wants to send to Test. The 3 modules will be included in the Main Development Version, but the Integrated Test Version will only have the Purchases module.
To make this decision, the Integrated Test team leader has to choose which objects of the Main Development Version will be sent to Integrated Test and perform the steps indicated on this page.