Free Preparation Discussions
MENU
iSQI CTFL_Syll2018 Exam Questions
- Topic 1: Apply equivalence partitioning to derive test cases from given requirements/ Identify typical objectives of testing
- Topic 2: Identify factors that influence the effort related to testing/ Describe the test activities and respective tasks within the test process
- Topic 3: Give examples of potential entry and exit criteria/ Describe the role of impact analysis in maintenance testing
- Topic 4: Explain the value of statement and decision coverage/ Distinguish between the root cause of a defect and its effects
- Topic 5: Recognize the different roles and responsibilities in a formal review/ Identify the tasks of a test manager and tester
- Topic 6: Recognize that functional, non-functional and white-box tests occur at any test level/ Identify the psychological factors that influence the success of testing
- Topic 7: Recall characteristics of good testing that are applicable to any life cycle model/ Explain how to derive test cases from a use cases
- Topic 8: Use examples to describe the value of static testing/ Apply a review technique to a work product to find defects
Free iSQI CTFL_Syll2018 Exam Actual Questions
Note: Premium Questions for CTFL_Syll2018 were last updated On Mar. 28, 2025 (see below)
Which of the following statements gives the BEST example of a trigger for maintenance testing?
You are testing a mobile app that displays a person's status in respect of Covid-19. There are five possibilities: Fully Vaccinated, Partly Vaccinated, Infected & Recovered. Last Tested Positive or Last Tested Negative. You have found that, after receiving data about successful administration of a second injection, the person's status has not changed from Partly Vaccinated to Fully Vaccinated, although it should have done. The project uses a popular proprietary defect management tool where you have drafted an incident report with the following information:
* Test id., test environment used and date/time of run
* Expected and actual results with steps to reproduce.
* Severity level 4 (Critical - an entire functional area is unusable)
* Version data for the application under test and the testware that was used
Which one of the following important items of information is missing?
Priority is an important item of information that is missing from the incident report. Priority indicates the importance or urgency of resolving the incident, based on the business needs and the impact on the stakeholders. Priority is usually assigned by the project manager or the customer, and it helps to determine the order in which incidents should be addressed. Priority may differ from severity, which indicates the degree of impact of the incident on the system or the component under test. Severity is usually assigned by the tester or the developer, and it helps to assess the risk of the incident. For example, an incident may have a high severity but a low priority, if it affects a critical function but only occurs in a rare situation. Conversely, an incident may have a low severity but a high priority, if it affects a minor function but occurs frequently or affects many users. Therefore, both priority and severity are useful information for incident management and resolution.
The other options are not essential information for the incident report, although they may be helpful or desirable in some cases. Recommendations are suggestions or proposals for resolving the incident, which may be provided by the tester, the developer, or other stakeholders. However, recommendations are not mandatory, and they may not be feasible or acceptable in some situations. Name of tester is the identifier of the person who reported the incident, which may be useful for communication or accountability purposes. However, name of tester is not critical, and it may be replaced by other identifiers, such as email address, employee number, or role. Change history is the record of the changes made to the incident report, such as status, resolution, or comments. Change history is valuable for tracking and auditing purposes, but it is not part of the initial incident report, rather it is updated as the incident progresses.
An airline's frequent flyer's club awards benefits depending on which tier a customer is in. The software must determine which tier to allocate a customer to based on an input value of total Credits Earned to date
Customers initially join the Silver Tier and remain in that tier for the first 400 Credits Earned The next 400 Credits Earned moves the customer into the Gold Tier. The next 600 Credits Earned moves the customer into the Platinum Tier Further Credits Earned moves the customer into the Concierge Tier.
Test Cases have been written with the following total Credits Earned input values:
TC1 -400 Credits
TC2 - 500 Credits
TC3 - 800 Credits
TC4-1500 Credits
Applying the Equivalence Partitioning test design technique, what percentage of valid Equivalence Partitions have these 4 test cases collectively achieved?
Equivalence Partitioning is a black-box test design technique that divides input data of a software module into partitions of equivalent data from which test cases can be derived. In this context, the valid equivalence partitions are:
Silver Tier: 0 to 400 Credits
Gold Tier: 401 to 800 Credits
Platinum Tier: 801 to 1400 Credits
Concierge Tier: 1401+ Credits
The test cases provided cover all these partitions:
TC1 covers the Silver Tier boundary at 400 Credits.
TC2 covers within the Gold Tier at 500 Credits.
TC3 covers the Gold Tier boundary at 800 Credits.
TC4 covers within the Concierge Tier at 1500 Credits.
Since all valid partitions are covered by the test cases, 100% of the valid Equivalence Partitions have been achieved.
Which one of the following is an example of how product risk analysis can influence the testing approach?
The other options are not examples of how product risk analysis can influence the testing approach, because they are either not related to product risks or not based on risk levels. They are:
Tests have been specified for the latest software release and users have prioritised these
However, there are some dependencies between tests as shown in the table below (e.g. Test ID. X cannot be run until Test ID. Y has been successfully completed).
Which test execution schedule best meets the prioritisation and dependency conditions?
The test execution schedule should follow the priority order of the tests, as well as the dependency constraints. The priority order is given by the user value column, where higher values indicate higher priority. The dependency constraints are given by the dependency column, where a test ID indicates that the test cannot be run until the test with that ID has been successfully completed. Therefore, the test execution schedule should start with the highest priority test that has no dependency, which is test 5. Then, it should continue with the next highest priority test that has no dependency or has a satisfied dependency, which is test 1. Then, it should proceed with test 2, which depends on test 1, and then test 3, which depends on test 2. Finally, it should end with test 4, which depends on test 3. Thus, the test execution schedule that best meets the prioritisation and dependency conditions is 5,1,2,3,4.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Tawna
7 days agoMaryanne
20 days agoTommy
23 days agoDomonique
1 months agoWerner
2 months agoDortha
2 months agoRochell
2 months agoAlison
2 months agoChristiane
3 months agoJerry
3 months agoMarta
3 months agoJaclyn
3 months agoBettina
4 months agoPhyliss
4 months agoJenifer
4 months agoRolland
4 months agoLashaun
4 months agoAudra
5 months agoCasie
5 months agoRashad
5 months agoFletcher
5 months agoRonny
5 months agoLanie
6 months agoWilliam
6 months agoEzekiel
6 months agoElenor
6 months agoEladia
6 months agoDarrin
7 months agoTamesha
7 months agoYvonne
8 months agoFranchesca
9 months agoRosendo
9 months agoColette
9 months agoJesusa
10 months ago