CTFL_Syll2018 - ISTQB Certified Tester Foundation Level (Syllabus 2018)

Testing the ease of modification of systems is the statement that is least likely to be true of non-functional testing. Non-functional testing is testing of the non-functional aspects of a system or software component, such as performance, usability, reliability, security, etc. Non-functional testing does not usually include testing the ease of modification of systems, as this is more related to maintainability, which is a quality attribute rather than a non-functional requirement1 defines non-functional testing as follows:

Non-functional Testing is defined as a type of Software testing to check non-functional aspects (performance, usability, reliability, etc) of a software application. It is designed to test the readiness of a system as per nonfunctional parameters which are never addressed by functional testing.

Non-functional Testing involves testing of non-functional requirements such as Load Testing, Stress Testing, Security, Volume, Recovery Testing etc. The objective of NFT testing is to ensure whether the response time of software or application is quick enough as per the business requirement.

A, B, and D are incorrect answers. Evaluating the interaction of various specified components (A), testing how the system works (B), and performing at unit, integration, system and acceptance test levels (D) are statements that are likely to be true of non-functional testing. Non-functional testing can cover the interaction of various components in terms of performance, reliability, compatibility, etc. Non-functional testing can test how the system works in terms of speed, efficiency, stability, etc. Non-functional testing can be performed at different test levels depending on the scope and objectives of the test.

Checking that at least 50% of decisions have been exercised by a test case suite is not a valid use of decision coverage, because it does not meet the minimum criterion of decision coverage, which is to exercise all possible outcomes of each decision in the software under test1 . Decision coverage is a technique that measures how much of the logic or branching of the software under test has been exercised by the test cases1 . The other options are valid uses of decision coverage. Option A is a valid use of decision coverage, because it can check that all decisions have been exercised in a single program1 . Option B is a valid use of decision coverage, because it can check that all decisions have been exercised in a business process1 . Option C is a valid use of decision coverage, because it can check that all calls from one program module to another have been made correctly1 .

They should be involved in reviewing requirements or user stories as soon as drafts are available is the option that represents good testing practice for testers, irrespective of the software lifecycle model used, because it allows testers to provide early feedback, identify potential defects, and clarify test objectives and scope1 . Early involvement of testers in reviewing requirements or user stories can improve the quality and testability of the software and reduce the cost and effort of testing1 . The other options do not represent good testing practice for testers, irrespective of the software lifecycle model used. Option A is not a good option, because they should start test analysis as early as possible, not when the corresponding development level is complete, to avoid delays and inefficiencies in testing1 . Option C is not a good option, because they should ensure that different test objectives apply to each test level, not the same test objectives, to avoid redundancy and gaps in testing1 . Option D is not a good option, because they should minimize the ratio of development levels to test levels to reduce project costs, but rather balance the development and test levels according to the project needs and risks1 .