iSQI CTFL_Syll2018 Exam With Confidence Using Practice Dumps

 Functional testing to test security at the system level, load testing at the system level to ensure the system availability is acceptable, regression testing at all levels, structure based testing at the component level only are the test types that will be required during the development1. A bank is developing a new service that will be delivered via the web. The user interactions are defined as a set of use cases and the service is designed to be available continuously 24/7. In view of the challenging characteristics of the service, the test manager has decided that the code should be thoroughly tested at component level. Therefore, the following test types will be required during the development:

• Functional testing to test security at the system level: This type of testing verifies that the software product performs its intended functions according to the user requirements and expectations1. Security is one of the functional aspects that needs to be tested at the system level, as it ensures that the software product protects itself from unauthorized access or harm1.
• Load testing at the system level to ensure the system availability is acceptable: This type of testing verifies that the software product can handle the expected or peak load of users or transactions without degrading its performance or functionality1. Availability is one of the quality attributes that needs to be tested at the system level, as it measures how well the software product performs its intended functions under specified conditions without interruption or failure1.
• Regression testing at all levels: This type of testing verifies that previously tested software still performs correctly after changes or defect corrections1. Regression testing is required at all levels of testing, as changes or defect corrections can introduce new defects or affect existing functionality1.
• Structure based testing at the component level only: This type of testing uses the structure or logic of the source code as a test basis to derive test cases and measure test coverage1. Structure based testing is required at the component level only, as the test manager has decided that the code should be thoroughly tested at component level to ensure its quality and reliability1.

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

How to fix the defect is not needed to specify in a defect report because it is not part of the information that is required to describe, reproduce, and prioritize the defect. How to fix the defect is part of the solution or resolution that is provided by the developers or maintainers who are responsible for correcting the defect. A defect report is a document that records and communicates the details of a defect found during testing. A defect report typically includes the following information:

• Defect ID: A unique identifier for the defect
• Summary: A brief description of the defect
• Severity and priority: An indication of how serious and urgent the defect is
• Test environment details: A description of the hardware, software, network, data, tools, etc., that were used when the defect was found
• How to reproduce the defect: A step-by-step procedure to recreate the defect
• Expected and actual results: A comparison of what should have happened and what actually happened when the defect occurred
• Attachments: Any additional information or evidence that can help understand or resolve the defect, such as screenshots, logs, files, etc.

You can find more information about defect reports in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 5.