| Both sides previous revision Previous revision Next revision | Previous revision |
| 2500_config_apps:0200_work_bsv:0600_testing_bsv [2022/08/21 22:48] – ↷ Page moved from docs:2500_config_apps:0200_work_bsv:0600_testing_bsv to 2500_config_apps:0200_work_bsv:0600_testing_bsv administrator | 2500_config_apps:0200_work_bsv:0600_testing_bsv [2026/08/13 00:55] (current) – ↷ Links adapted because of a move operation localdev |
|---|
| ====== Testing Business Space Version ====== | ====== Testing Business Space Version ====== |
| |
| Once you are happy with your changes to the business space version you can make the version available for testing. You may need to test the version in order to make sure that your business rules and processes work as expected, presentations and reports look good etc. It is recommended that you always test your version prior to publishing it for the end users. Once the version has been made available for testing its state changes to ''UNDER TEST'', and you can now try creating instances of different business objects from this version, run processes, reports etc in the Operation Mode (see [[docs:2000_concepts:1000_config_proc:0300_testing_mode|Testing Mode]]). Instances of objects created during testing are stored in a separate database so the operational data of the end users is not affected by any testing activity – see also [[docs:2500_config_apps:0200_work_bsv:0100_bsv_lifecycle|Lifecycle of a Business Space Version]]. | Once you are happy with your changes to the business space version you can make the version available for testing. You may need to test the version in order to make sure that your business rules and processes work as expected, presentations and reports look good etc. It is recommended that you always test your version prior to publishing it for the end users. Once the version has been made available for testing its state changes to ''UNDER TEST'', and you can now try creating instances of different business objects from this version, run processes, reports etc in the Operation Mode (see [[2000_concepts:1000_config_proc:0300_testing_mode|Testing Mode]]). Instances of objects created during testing are stored in a separate database so the operational data of the end users is not affected by any testing activity – see also [[2500_config_apps:0200_work_bsv:0100_bsv_lifecycle|Lifecycle of a Business Space Version]]. |
| |
| To make a version available for testing: | To make a version available for testing: |
| |
| - Click on the version you want to test in the Elements Tree to select it (make sure that the version is loaded – see [[docs:2500_config_apps:0200_work_bsv:0300_loading_bsv|Loading Business Space Version]]). | - Click on the version you want to test in the Elements Tree to select it (make sure that the version is loaded – see [[2500_config_apps:0200_work_bsv:0300_loading_bsv|Loading Business Space Version]]). |
| - Select “Version/Put under Test” in the menu or right click to bring up the pop-up menu and select “Put under Test”. | - Select “Version/Put under Test” in the menu or right click to bring up the pop-up menu and select “Put under Test”. |
| - If you already have a version in this business space in the ''UNDER TEST'' state, you will be offered a choice of whether to copy the operation data from the existing test version or create the test version with no operational data at all. If you already had some test instances of business objects from the previous rounds of testing it may be helpful to use the same instances during the new round. Once you select the required option the version will be moved to the ''UNDER TEST'' state (this may take some time) and displayed in pink. | - If you already have a version in this business space in the ''UNDER TEST'' state, you will be offered a choice of whether to copy the operation data from the existing test version or create the test version with no operational data at all. If you already had some test instances of business objects from the previous rounds of testing it may be helpful to use the same instances during the new round. Once you select the required option the version will be moved to the ''UNDER TEST'' state (this may take some time) and displayed in pink. |
| If your business space version has already been in the ''UNDER TEST'' state before //**Aware IM**// will display a dialog asking you whether to perform integrity checking of the version and whether to use the existing data for testing or clear the testing data. If you are going through many testing cycles during development and put version in and out of testing many times then constantly answering the questions of this dialog can be tedious. To avoid the dialog and to get //**Aware IM**// to use the default values (no integrity checking and using the existing data for testing) you can use the “Put under Test (quickly)” command available in the main menu or in the popup menu instead of the “Put under Test” command. You can also use the Ctrl+Q shortcut to make it even quicker. | If your business space version has already been in the ''UNDER TEST'' state before //**AwareIM**// will display a dialog asking you whether to perform integrity checking of the version and whether to use the existing data for testing or clear the testing data. If you are going through many testing cycles during development and put version in and out of testing many times then constantly answering the questions of this dialog can be tedious. To avoid the dialog and to get //**AwareIM**// to use the default values (no integrity checking and using the existing data for testing) you can use the “Put under Test (quickly)” command available in the main menu or in the popup menu instead of the “Put under Test” command. You can also use the Ctrl+Q shortcut to make it even quicker. |
| |
| ===== Embedded Testing ===== | ===== Embedded Testing ===== |