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

What is The Fundamentals of Software Testing?  - Part 2 Please refer to part 1 before reading any further! Evaluating exit criteria and reporting:   The test “exit criteria” (established during “Test planning and control”) indicate that testing is complete.  Test closure activities: Ensure that all documentation has been correctly completed  Close down and archive the test environment, infrastructure and testware Hand over testware to maintenance team  Log lessons learned The psychology of testing:   Selecting the appropriate individual(s) to perform the tests, and communicating the results of the tests to the developers, requires a basic understanding of the psychology of testers and developers. The ISEB Software Testing guidance provides a hierarchy of ‘independence’ – that is, a list of individuals who could potentially test the software, gradated according to their perceived level of detachment from the development proces...

What is The Fundamentals of Software Testing? - Part 1   “The Fundamentals of Software Testing ” is the first module of the ISEB Software Testing Foundation course and examination syllabus. ISEB recommend that Software Testing Foundation students spend 20% of their study time on the Software Testing Fundamentals course section. “The Fundamentals of Software Testing” is also the title of the opening chapter in the official ISEB Software Testing manual. Understanding the fundamentals of software testing is clearly crucial to achieving proficiency according to the ISEB software testing professional standards. But what, precisely, are these “fundamentals” of software testing, and what do you need to know in order to pass the ISEB Software Testing Foundation examination? Why is testing necessary? According to Peter Morgan (freelance testing practitioner and member of the ISEB Software Testing Accreditation and Examination panel), an unnecessarily high proportion o...

Equivalence Partitioning Equivalence partitioning uses a model of the component that partitions the input and output values of the component.   The input and output values are derived from the specification of the component's behaviour. The model shall comprise partitions of input and output values.   Each partition shall contain a set or range of values, chosen such that all the values can reasonably be expected to be treated by the component in the same way (i.e. they may be considered 'equivalent').   Both valid and invalid values are partitioned in this way. Test cases shall be designed to exercise partitions.   A test case may exercise any number of partitions.   A test case shall comprise the following:            - the input(s) to the component:          -   the partitions exercised:          -   the expected ...