Pass the iSQI CTFL2018 CTFL_Syll2018 Questions and answers with CertsForce

Explanation of Correct Answer: A benefit of running tests with a test automation tool is that the time spent on repetitive tasks is reduced, as the tool can execute tests faster and more reliably than humans. Therefore, option D is correct. Option A is incorrect, as test coverage is not increased by using a test automation tool, but by designing more effective test cases. Option B is incorrect, as the number of found bugs is not reduced by using a test automation tool, but by improving the quality of the software under test. Option C is incorrect, as the total cost of the test project does not always decrease by using a test automation tool, as there are costs associated with developing and maintaining the automated tests.

References: Certified Tester Foundation Level Syllabus, Section 6.1

Integration testing is the process of testing the interactions between different components or subsystems of a system. It has the following characteristics:

It can be done in an incremental manner, meaning that components or subsystems are integrated and tested one by one until the whole system is integrated and tested.

It is usually done before system testing, which is the process of testing the system as a whole against its requirements and specifications.

It includes functional tests, which are tests that verify the functionality and behavior of the system or its components.

It includes non-functional tests, which are tests that verify the quality attributes of the system or its components, such as performance, reliability, security, etc.

Therefore, statements I, III, and IV are correct.

References: Certified Tester Foundation Level Syllabus, Section 5.1.2 and 5.2.2

Acceptance tests are the test types that call for involvement of an expert from the financial department for a new system that deals with all financial transactions in a company. Acceptance tests are tests conducted to determine if the requirements of a specification or contract are met by a system or software component prior to its delivery or deployment. Acceptance tests are usually performed by end users or customers who have domain knowledge and expertise in evaluating if the system meets their needs and expectations1 defines acceptance tests as follows:

Acceptance Testing is a level of software testing where a system is tested for acceptability. The purpose of this test is to evaluate the system’s compliance with the business requirements and assess whether it is acceptable for delivery.

Acceptance Testing is also known as User Acceptance Testing (UAT), End-User Testing, Operational Acceptance Testing (OAT) or Field (Acceptance) Testing.

Acceptance Testing is performed by end users or customers who have domain knowledge and expertise in evaluating if the system meets their needs and expectations.

A, C, and D are incorrect answers. Component testing, maintenance testing, and system testing are not test types that call for involvement of an expert from the financial department for a new system that deals with all financial transactions in a company. Component testing is testing of individual software components in isolation from other components, usually done by developers. Maintenance testing is testing of a modified system or component after changes have been made to it, usually done by testers. System testing is testing of an integrated system as a whole to verify that it meets specified requirements, usually done by testers.

Static testing is testing of a component or system at a specification or implementation level without execution of that software. Requirements review is an example of static testing, because it involves checking the quality and completeness of the requirements specification document without executing the software.

Test analysis and design is the activity in the fundamental test process that includes identifying necessary test data. Test data are the inputs that are used to execute the test cases and verify the expected results2 defines this activity as follows:

Test analysis and design has the following major tasks:

Reviewing the test basis (such as requirements, risk analysis reports, design documents or code).

Identifying test conditions based on analysis of test items, specifications, behavior and structure of the software.

Designing high-level test cases based on test conditions and designing techniques.

Evaluating testability of requirements and system under test.

Defining exit criteria.

Evaluating exit criteria and reporting (A) is part of the test closure activities, where the results of testing are evaluated against the defined objectives. Test implementation and execution (B) is where the test cases are executed using the identified test data and deviations from expected results are documented. Test planning and control © is where the overall approach and resources for testing are defined and monitored.

 According to the syllabus, dynamic analysis tools are tools that perform testing or analysis by executing the software or a part of it. Dynamic analysis tools can help detect defects or problems that only appear during runtime, such as memory leaks, performance issues, concurrency errors, etc. The answer A is correct because it suggests using a dynamic analysis tool for detecting a memory leak during performance testing. A memory leak is a situation where a code component fails to release memory after it has finished using it, causing memory exhaustion and degradation of performance. A dynamic analysis tool can monitor the memory usage of the code component and identify any memory leaks. The other answers are incorrect because they suggest using tools that are not suitable for detecting memory leaks during performance testing. A test execution tool is a tool that executes test cases automatically or semi-automatically. A configuration management tool is a tool that controls and tracks changes to the software components and documentation. A coverage measurement tool is a tool that measures how much of the code or functionality has been exercised by a test suite.

References: Certified Tester Foundation Level Syllabus, Section 4.6.1, page 53-54.

A unit test framework tool is a tool that supports the creation, execution and reporting of unit tests, which are tests that verify the functionality and quality of individual functions or methods in source code. A unit test framework tool can detect defects such as syntax errors, logic errors, boundary violations, etc.

Having an independent test function in an organisation can improve defect finding during reviews and testing, because independent testers can provide a different perspective and have less bias than developers or other stakeholders. Independent testers can also focus on testing activities without being influenced by development pressures or deadlines12. The other options are not valid reasons for having an independent test function. Option B is more related to code reviews, which can be done by developers themselves or by peers. Option C is not beneficial, because communication between developers and testers is essential for effective testing and defect resolution. Option D is not directly related to the test function, but to the test management and reporting processes12.

Reviewing tests developed by others would not typically be performed by a tester, but rather by a test leader or a peer reviewer1 . Reviewing tests developed by others is an activity that involves checking the quality and completeness of the test cases or procedures and providing feedback or suggestions for improvement1 . The other options are tasks that would typically be performed by a tester. Option A is a task that would typically be performed by a tester, because it involves preparing and acquiring the test data that are needed for executing the test cases or procedures1 . Option B is a task that would typically be performed by a tester, because it involves setting up and checking the test environment that supports the execution of the test cases or procedures1 . Option C is a task that would typically be performed by a tester, because it involves writing test summary reports that document the results and outcomes of the test execution1 .

Using boundary analysis for x, the test cases are required to cover the values on and around the boundaries of x > 0 and x < 100. Therefore, the test cases should include -1, 0, 1, 99, 100, and 101. The value 0.1 is not a boundary value, and the values -500 and 500 are too far from the boundaries to be relevant.

References: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB, Section 4.2.2, Page 34