[Apr 04, 2024] Genuine CTFL_Syll2018 Exam Dumps Free Demo
Printable & Easy to Use ISQI CTFL2018 CTFL_Syll2018 Dumps 100% Same Q&A In Your Real Exam
ISQI Certified Tester Foundation Level (CTFL_Syll2018) exam is a certification exam for software testers. CTFL_Syll2018 exam is intended for those who want to gain a solid foundation in software testing and improve their skills and knowledge in this field. CTFL_Syll2018 exam is based on the ISTQB (International Software Testing Qualifications Board) syllabus for the foundation level, which was updated in 2018.
NEW QUESTION # 210
Which of the following statements is true?
- A. It is impossible to achieve 100% statement coverage
- B. 100% branch coverage means 100% statement coverage and vice-versa.
- C. 100% branch coverage means 100% statement coverage.
- D. 100% statement coverage means 100% branch coverage.
Answer: C
Explanation:
100% branch coverage means 100% statement coverage, but not vice-versa. Branch coverage is a stronger criterion than statement coverage, as it requires that every possible outcome of each decision point is executed at least once. Statement coverage only requires that every executable statement is executed at least once1 explains this as follows:
Branch Coverage (also known as Decision Coverage) measures which possible branches in flow control structures are followed. Branch Coverage is a testing method, which aims to ensure that each one of the possible branch from each decision point is executed at least once and thereby ensuring that all reachable code is executed.
Statement Coverage measures the number of statements in the source code that are executed during the test.
Statement Coverage is a metric, which is used to calculate and measure the number of statements in the source code which have been executed during testing.
B, C, and D are false statements. 100% statement coverage does not mean 100% branch coverage (B), as there may be some branches that are not covered by the test cases. 100% branch coverage does not mean 100% statement coverage and vice-versa, as branch coverage implies statement coverage but not the other way around. It is possible to achieve 100% statement coverage (D), but it may not be feasible or cost-effective for some systems.
NEW QUESTION # 211
Which of the following is an example of Static testing?
- A. Performance testing
- B. Usability testing
- C. Calculating path coverage using tools
- D. Requirements review
Answer: D
Explanation:
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.
Reference: A Study Guide to the ISTQB Foundation Level 2018 Syllabus1, Chapter 2, Section 2.3.
NEW QUESTION # 212
Consider the following Pseudo code:
How many minimum lea cases are required to cover 100% Statement coverage and Decision coverage?
- A. 1 for Statement. 2 for Decision
- B. 1 for Statement. 5 for Decision
- C. 2 for Statement, 5 for Decision
- D. 5 for Statement. 1 for Decision
Answer: C
NEW QUESTION # 213
When should component integration tests be carried out?
- A. Integration tests should always be done before system tests
- B. Integration tests should be done at the customer's site, after acceptance tests
- C. Integration tests can be done before or after system tests
- D. Integration tests should always be done after system tests
Answer: A
Explanation:
Explanation
Component integration testing is the process of testing the interactions between different components of a system. It should always be done before system testing, which is the process of testing the system as a whole.
Integration testing can reveal defects in the interfaces and interactions between components, which can affect the functionality and performance of the system. System testing can reveal defects in the system requirements, design, and behavior, which can affect the quality and usability of the system. Therefore, it is logical to perform integration testing before system testing, to ensure that the components work together correctly before testing the system as a whole.
References: Certified Tester Foundation Level Syllabus, Section 5.1.2 and 5.2.2
NEW QUESTION # 214
Consider the following pseudo code
1. Begin
2. Read Gender
3. __Print "Dear"
4. If Gender = 'female'
5. Print ("Ms")
6. Else
7. __Print ( "Mr")
8. Endif
9. End
How many test cases are needed to achieve 100 per cent decision coverage?
- A. 0
- B. 1
- C. 2
- D. 3
Answer: D
Explanation:
Explanation
Decision coverage is a structure-based test technique that involves testing every decision point in the code by testing all possible outcomes or branches of each decision point. Decision coverage requires some knowledge of the internal structure or implementation of the software system; it focuses on how the system does what it does rather than what it does.
The pseudo code given in the question has one decision point at line 4, where the value of Gender is compared to 'female'. This decision point has two possible outcomes or branches:
True branch: If Gender = 'female', then print "Ms" at line 5.
False branch: If Gender != 'female', then print "Mr" at line 7.
To achieve 100 per cent decision coverage, we need to test both outcomes or branches of the decision point at least once. Therefore, we need two test cases that cover both scenarios:
TC1: Gender = 'female' -> Print "Dear Ms"
TC2: Gender = 'male' -> Print "Dear Mr"
The other options are not correct because they do not provide enough or too many test cases to achieve 100 per cent decision coverage. For example:
A). 1: This option is not enough because it only provides one test case that covers one outcome or branch of the decision point, but not the other.
C). 3: This option is too many because it provides three test cases that cover both outcomes or branches of the decision point, but one of them is redundant or unnecessary.
D). 4: This option is too many because it provides four test cases that cover both outcomes or branches of the decision point, but two of them are redundant or unnecessary.
You can find more information about decision coverage and structure-based testing in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.3.
NEW QUESTION # 215
Which of the following statements is correct?
- A. Pair programming is, among other things, an informal review method.
- B. Pair programming is used usually in waterfall model
- C. Pair programming is done with developer and tester pairing together
- D. Pair programming is an alternative term for code inspection.
Answer: A
Explanation:
Pair programming is a software development technique where two programmers work together on the same code at the same workstation. One programmer, called the driver, writes the code while the other programmer, called the navigator, reviews the code and provides feedback and suggestions. Pair programming is not only a coding technique but also an informal review method because it involves constant communication and collaboration between the programmers who check each other's work and share their knowledge and skills.
Pair programming can improve the quality and productivity of software development by reducing defects, increasing code readability, enhancing learning opportunities, and fostering creativity and innovation. Pair programming is usually used in agile methods such as Extreme Programming (XP), Scrum, or Kanban. It is not an alternative term for code inspection, which is a formal review method where a group of reviewers examine a piece of code in a structured and systematic way following predefined rules and roles. It is also not done with developer and tester pairing together because pair programming requires both programmers to have similar levels of expertise and familiarity with the code they are working on. You can find more information about pair programming in A Study Guide to the ISTQB Foundation Level 2018 Syllabus, Chapter 31.
NEW QUESTION # 216
You are testing an e-commerce system which sporadically fails to properly manage customers' shopping carts.
You have stressed the urgency of this situation to the development manager and development team and they recognize the priority in getting this resolved. The development team is waiting for more information in your defect report in order to help resolve this failure.
Given the following items of information:
1. The expected results
2. The actual results
3. The urgency and priority to fix this
4. The date and author of the defect report
5. A description of the defect in order to reproduce, including screenshots and database dumps Which of the items would be MOST useful to include in the defect report?
- A. 1, 2, 4
- B. 1,2, 3, 4, 5
- C. 1, 2, 5
- D. 3, 4
Answer: C
Explanation:
The correct answer is A, as it includes the items that would be most useful to include in the defect report. A defect report is a document that describes and records any anomaly found during testing2. A defect report typically includes information such as:
* The expected results
* The actual results
* A description of the defect in order to reproduce, including screenshots and database dumps These items are useful to include in the defect report, as they help the developers to understand and fix the defect2. Option B is incorrect, as it includes an item that would not be useful to include in the defect report. The urgency and priority to fix this is not useful to include in the defect report, as it is determined by the test manager or other stakeholders based on various factors such as severity, impact, risk, and business value2. Option C is incorrect, as it omits an item that would be useful to include in the defect report. The actual results are useful to include in the defect report, as they show what happened when the defect occurred2. Option D is incorrect, as it omits two items that would be useful to include in the defect report. The expected results and a description of the defect in order to reproduce are useful to include in the defect report, as they show what should have happened and how to replicate the defect2. References: 2, Section 2.9
NEW QUESTION # 217
Which statement about use case testing is true?
- A. The test cases are designed to find defects in the process flow
- B. The test cases are always designed by customers or end users
- C. The test cases are designed to be used by real users, not by professional testers
- D. The test cases are designed to find defects in the data flow.
Answer: A
Explanation:
Use case testing is a specification-based test technique that is based on the use cases or scenarios that describe how users interact with the system under test. Use case testing aims to find defects in the process flow or functionality of the system under test by verifying that it behaves as expected according to the use cases or scenarios. Use case testing does not require any knowledge of the data flow or structure of the system under test; it only focuses on what the system does rather than how it does it. Use case testing can be done by professional testers or real users, depending on the level and purpose of testing. Use case testing can also be designed by customers or end users, developers, testers, analysts, or anyone who has access to the use case specifications or user requirements. You can find more information about use case testing in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.2.
NEW QUESTION # 218
Which of the following is an appropriate reason for maintenance testing?
- A. Bugs found during unit testing
- B. Bugs found during system testing
- C. Bugs found during integration testing
- D. Bugs found in the field after upgrading the operation system
Answer: D
NEW QUESTION # 219
Which of the following metrics could be used to monitor progress along with test preparation and execution?
[K1]
- A. The total number of tests planned
- B. The total number of requirements to be tested
- C. The number of testers used for test execution so far
- D. The failure rate in testing already completed
Answer: D
Explanation:
Metrics are quantitative measures that can be used to monitor and control various aspects of software testing processes and products1. Metrics can be used to monitor progress along with test preparation and execution by providing information about the status of testing activities, such as test planning, test design, test execution, test evaluation, defect management, etc1. Among the options given in this question, only C is a suitable metric for monitoring progress along with test preparation and execution. The failure rate in testing already completed is a metric that measures how many tests have failed out of the total number of tests executed1. This metric can indicate the quality of the software product under test and the effectiveness of the test cases1. It can also help to identify areas that need more attention or improvement in testing1. Therefore, this metric can be used to monitor progress along with test preparation and execution.
NEW QUESTION # 220
Which of the following lists contains only black-box test techniques?
- A. Use case testing, Statement testing, State transition testing
- B. Exploratory testing. State transition testing, Control flow testing
- C. Decision table testing, Use case testing, State transition testing
- D. Decision table testing. Use case testing, Control flow testing
Answer: D
NEW QUESTION # 221
Given the following state transition diagram where SS is the start state:
Which of the following answers describes a test case that only uses valid transitions to exercise all states, using the minimum number of transitions?
- A. SS-S3-S2-S1.
- B. SS-S1-S2-S3.
- C. SS-S3-SS-S1-S3-S2.
- D. SS-S1-S3-S2.
Answer: D
Explanation:
Explanation
According to the syllabus, state transition testing is a technique that tests the behaviour of a system or component based on its transitions between states. A state transition diagram is a graphical representation of the states and transitions of a system or component. A test case that uses valid transitions to exercise all states should cover all the nodes and edges in the diagram. The answer D is correct because it covers all the four states (SS, S1, S2, S3) and all the five transitions (SS-S1, S1-S3, S3-S2, S2-SS, SS-S3) in the diagram. The other answers are incorrect because they either miss some states or transitions or use more transitions than necessary.
References: Certified Tester Foundation Level Syllabus, Section 4.4.1, page 47-48.
NEW QUESTION # 222
What is a "test harness"?
- A. A general name for test data that is used by the test cases.
- B. A test environment comprised of stubs and drivers needed to execute a test.
- C. A detailed description of a test case to enable its execution by non-expert tester.
- D. One of the topics that needs to be covered in the final Test Report.
Answer: D
NEW QUESTION # 223
While reporting a defect, which of the following indicates the level of business importance assigned to the defect?
- A. Priority
- B. Urgency
- C. Severity
- D. Difficulty
Answer: A
Explanation:
Explanation of Correct Answer: Priority indicates the level of business importance assigned to the defect, while severity indicates the degree of impact that a defect has on the development or operation of a component or system. Urgency is not a standard term used in defect reporting, and difficulty refers to the effort required to fix the defect.
References: Section 1.4.3.2, Section 5.3.2
NEW QUESTION # 224
The flow graph below shows the logic of a program for which 100% statement coverage and 100% decision coverage is required on exit from component testing. [K4] The following test cases have been run:
Test Case 1 covering path P,Q,R,U
Test Case 2 covering path P,Q,S,V
Test Case 3 covering path P,Q,S,W,X
Test case 4 covering path P,Q,S,W,Y
Refer to the exhibit
- A. Statement coverage is 100%; decision coverage is 100%
- B. Statement coverage is 100%; decision coverage is less than 100%
- C. Statement coverage and decision coverage are both less than 100%
- D. Statement coverage is less than 100%; decision coverage is 100%.
Answer: C
NEW QUESTION # 225
After a record of poor-quality software releases (incorrect menu selection options, new features that do not work, users allowed to change security levels without administrator rights), you have been asked to review the test capability in your company.
You have limited time to do the review before the next project, which type of testing would be MOST appropriate to review first?
- A. Non-functional testing.
- B. Functional testing.
- C. Performance testing.
- D. Structural testing.
Answer: B
Explanation:
Functional testing is the most appropriate type of testing to review first, after a record of poor-quality software releases. Functional testing is a type of testing that verifies the functionality and behavior of the software against its requirements and specifications. Functional testing can help detect defects such as incorrect menu selection options, new features that do not work, users allowed to change security levels without administrator rights, etc. Functional testing can also help improve the user satisfaction and confidence in the software.
Therefore, functional testing should be reviewed first to ensure that it is done effectively and efficiently, and that it covers all the relevant aspects of the software functionality.
References: Certified Tester Foundation Level Syllabus, Section 2.3 and 5.2.2
NEW QUESTION # 226
......
CTFL_Syll2018 Practice Test Give You First Time Success with 100% Money Back Guarantee!: https://www.practicematerial.com/CTFL_Syll2018-exam-materials.html
All Obstacles During CTFL_Syll2018 Exam Preparation with CTFL_Syll2018 Real Test Questions: https://drive.google.com/open?id=15g1m1Ra_BXfQEbUWqWHZv_BLZ5KLEJ8p
