Pass the iSQI CTFL2018 CTFL_Syll2018 Questions and answers with ExamsMirror

The statement that incidents cannot be raised during development is not true, because incidents can be raised during any stage of software development life cycle where deviations from expected or desired behaviour are observed . Incidents can be raised during development, review, testing or use of a software product . The other options are true statements about incidents. 

Load testing tool checks for time response and resource utilization of a system under a specific load condition or scenario. Load testing tool can simulate multiple users accessing or performing operations on a system concurrently and measure how long it takes for the system to respond and how much CPU, memory, disk or network resources are consumed by the system.

Test planning and control, Test analysis and design, Test implementation and execution, Evaluating exit criteria and reporting, Test closure activities are the phases of the ISTQB fundamental test process. The fundamental test process is a generic model that describes the basic activities and tasks involved in testing software systems. defines these phases as follows:

Test planning and control: This phase involves defining test objectives, scope, strategy, resources, schedule, risks, metrics etc., as well as monitoring and controlling test activities throughout the test process.

Test analysis and design: This phase involves reviewing test basis such as requirements specifications or user stories , identifying test conditions based on analysis of test items , specifications , behavior and structure of software , designing high-level test cases based on test conditions and designing techniques , evaluating testability of requirements and system under test , defining exit criteria .

Test implementation and execution: This phase involves developing and prioritizing test cases , creating test data and writing test procedures , checking test environment has been set up correctly , executing test cases

In a Scrum development life cycle model, regression testing is an increasingly important activity as the project progresses. Scrum is an agile framework that follows an iterative and incremental approach to software development, where the software is delivered in small units called sprints. Regression testing is a type of testing that verifies that previously tested software still performs as expected after changes or modifications. Regression testing is essential in Scrum, as new features or functionalities are added or modified in each sprint, which can introduce new defects or affect existing ones. Therefore, regression testing should be performed at the end of each sprint, as well as before releasing the software, to ensure that the software meets the quality standards and user expectations.

References: Certified Tester Foundation Level Syllabus, Section 5.3.2

It is a project risk since successful completion of the project depends on successful and timely completion of the tests. defines project risks as follows:

Project risks are risks that affect the project schedule, resources, or budget. They can be related to the project management process, such as planning, estimation, communication, or monitoring. Project risks can also be related to external factors, such as dependencies, stakeholders, vendors, or regulations.

It is not a product risk (B and C), as product risks are risks that affect the quality or performance of the software product. defines product risks as follows:

Product risks are risks that affect the functionality, reliability, usability, efficiency, maintainability, or portability of the software product. They can be related to the software requirements, design, implementation, or testing. Product risks can also be related to user expectations, needs, or satisfaction.

It is not no longer a risk for the Test Manager (D), as the sub-contractor’s failure may still impact the Test Manager’s responsibilities and deliverables. The Test Manager should monitor and mitigate this risk as much as possible.

 The level of risk is determined by multiplying the impact of an adverse event by the likelihood of that event occurring1 . The impact of an adverse event is the degree of harm or loss that would result from the event, such as financial loss, reputation damage, legal consequences, or safety hazards1 . The likelihood of an adverse event is the probability or frequency of the event happening, based on historical data, expert judgement, or statistical analysis1 . The other options are not correct formulas for calculating risk. Option A confuses the cost of preventing an adverse event with its impact. Option B confuses the cost of possible legal action with its likelihood. Option D uses two synonyms for likelihood (probability and frequency) instead of combining it with impact.

The test execution schedule would not be expected to see on an incident report from test execution, because it is not related to the incident itself, but rather to the overall plan and progress of testing . An incident report is a document that records any event that deviates from the expected or desired behaviour of the software under test . The other options are information that would be expected to see on an incident report from test execution. Option A is expected, because the version(s) of the software under test can help to identify and reproduce the incident . Option C is expected, because the expected results and actual results can help to describe and demonstrate the incident . Option D is expected, because the precise steps to reproduce the problem can help to analyse and resolve the incident .

Agile development can be classified as an iterative incremental life cycle model, where each iteration delivers a working product increment that can be evaluated by stakeholders and users. describes this as follows:

Iterative Incremental Development Model is a process where creating requirements, designing, building and testing a system in small parts. This model divided into small parts which will help to make modules very easily.In this model, module passes through some phases like requirements, coding, designing, testing.

Agile Model mostly recommended to use for current software development industries because it is very realistic approach to develop any kind of software.It follows iterative approach which means whole project divided into small iterations or modules.

Agile development is not related to any life cycle model (A), RAD (B), or V model ©.

Introducing the tool to all the test teams of the organization at the same time is a factor that could negatively influence the success of the deployment of a tool within an organization, as it may cause resistance, confusion, or overload among the test teams. A better approach would be to introduce the tool gradually and incrementally, starting with a pilot project or a small group of users, and then expanding to other test teams based on the feedback and results. suggests this as follows:

A pilot project should be conducted before introducing a new test tool into an organization in order to learn more about how to use it effectively and efficiently in your context and how it will interact with other tools and processes. A pilot project should involve a small group of users who are willing and able to experiment with the tool and provide feedback. The pilot project should have clear objectives, scope, duration, and success criteria.

B, C, and D are factors that could positively influence the success of the deployment of a tool within an organization. Collecting usage information of the tool from the early projects (B) can help to evaluate the benefits and drawbacks of the tool, identify areas for improvement, and justify the investment. Providing training and coaching for new users of the tool © can help to increase their confidence and competence in using the tool, reduce errors and frustration, and enhance their productivity and satisfaction. Adapting and improving the processes to the usage of the tool (D) can help to optimize the workflow and performance of the test teams, align the tool with the organizational goals and standards, and increase the value and quality of the testing activities.

A typical characteristic of the walkthrough review type is that the meeting is led by the author. A walkthrough is a type of informal review that involves a presentation of a work product by the author to peers and other stakeholders for feedback and comments. The author leads the meeting and explains the work product to the participants, who can ask questions and make suggestions for improvement. The author may also record any issues or action items during the meeting. A walkthrough does not require formal preparation or follow-up by the participants, nor does it have defined entry and exit criteria.

References: Certified Tester Foundation Level Syllabus, Section 3.2.2