Software Testing Exam Study Blog For The BCS ISEB-ISTQB Certification

Beyond ISEB ISTQB-BCS: User Acceptance Testing (UAT) for Software Systems Part 2 Test Environment The test environment must be as similar to the production environment as possible. This is simple to accomplish when the application or system is installed on a user's computer but a little more difficult in a client server or hosted environment. The environment should have the same software, hardware, and network configuration as the production environment. The environment should have all the common or shared data from the production environment. It may be possible to simply port this data from QA to UAT. The UAT environment should also have sufficient privately owned data to enable testing. This may be done by selecting one customer to test on, or one product, and to port this data from the production environment where the new system replaces an existing one, or to create the data manually where a manual system is being replaced. Another approach is to simply port all the data i...

 Beyond ISEB ISTQB-BCS: User Acceptance Testing (UAT) for Software Systems Part 1 This is the first part of a 2 part article on User Acceptance Testing (UAT) of software systems. It follows my previous articles on Quality Management topics. Up to this point no-one outside the development and QA teams have test driven your new software system. You've proven that there are no glitches in the software by thoroughly unit and function testing it, you've proven that it is well integrated with integration testing, and you've even proven that it meets the requirements specified for it (or at least the QA groups interpretation of those requirements), but you still haven't passed the ultimate test: do the users like the system? Customer acceptance is critical when building a commercial product and still important when building an in-house system. New software systems are usually introduced to replace existing systems that users have become accustomed to. Changing the way the...

What is Acceptance Testing? Acceptance testing is normally the responsibility of the intended customer of the software under development. The testing is typically performed prior to the customer officially accepting the software product. The aim of this type of testing is not actually to find defects, but to provide a level of confidence in the software and to act as an assessment of the products readiness for deployment. A company may have paid a significant sum of money to a software development company to provide them with a product. So it is in the receiving company's best interests to perform some kind of test to ensure the product does what it was intended to do, and operates as expected. This type of testing may not be the last phase of software testing though, as depending on the software/system, an integration test may be required too. This type of software testing is also valid at other stages of the software development lifecycle, for example; A COTS(Comm...