And again about software testing

System testing of software is the black box testing conducted on a complete and fully integrated software product based on the software requirements specification. In main focus of this testing is to evaluate Business, Functional and End-user requirements implementation. In Software Development Life Cycle the System Testing performs as the first level of testing where the application is tested as a whole in environment that particularly resembles the effective production environment in order to check if developed software meets functional requirements and to test, validate and verify both the Application Architecture and Business requirements. Basically this is the full end to end testing on the software on the similar to production environment. System Testing preparation procedure: Write/Update System Test Plan based on project plan, test strategy & main test plan Create/Update test cases covering all functional, non-functional, technical & UI requirements and

UI testing is a very tricky thing. Everything depends on how accurately test tool recognizes UI elements and theirs properties. In this particular topic I would like to tell you how some invisible and not obvious settings of TestComplete can improve recognition of UI object properties. TestComplete with default settings does not always have access to Extended properties of these UI elements: You can change it by going to Tools > Current Project Properties > Object Mapping and check the required component there (if it is supported by TestComplete). After this you will be able to see additional category “Extended” in the Object Spy and access these properties in your test scripts: The only one thing you should take into account is that the designer of the Object Mapping tree was probably drunk or used a very heavy drugs. In some cases it is not enough to check the object category (I spend several days by trying to configure support of our DevExpress XtraG