Font size
WorksheetsCâu hỏi về ISTQB
Total questions: 73
Worksheet time: 2hrs 17mins
What is Testing? - Testing là gì
Why is Testing Necessary?
Seven Principles of Testing – 7 nguyên lý cơ bản của testing
Test Process
The Psychology of Testing
Software Development Lifecycle Models
Test Levels (K2)
Test Types
Maintenance Testing
Static Testing Basics
Review Process
Categories of Test Techniques
Who is ISTQB -ISTQB là gì?
Course structure -Exams in ISTQB
About Foundation level Examination -Về các mức độ kiến thức trong bài thi
Plan for examination- Lập kế hoạch cho kỳ thi
How to read and use ISTQB books- Cách đọc và sử dụng các cuốn sách ISTQB bằng tiếng Anh
Tips for doing exercises-Các chỉ dẫn, kinh nghiệm để làm bài tập
There are currently three levels of certification
The Foundation Level certification (one module)
Advanced Level certifications (three modules)
An Expert levels is currently be
Who is ISTQB?
A non-profit organization responsible for defining guidelines
A certification body for software testers
An international working group for testing standards
What does the ISTQB Certified Tester program provide?
Certification for software testers
Training for software developers
Guidelines for software testing
How many multiple choice questions are in the Foundation Level examination?
30
40
50
What is the pass mark for the Foundation Level examination?
60%
65%
70%
What is the duration of the Foundation Level examination?
60 minutes
75 minutes
90 minutes
What is the recommended preparation time for the exam?
1 month to 1.5 months
2 months to 3 months
1 week to 2 weeks
What is the focus of the study materials for ISTQB?
Remembering key concepts
Understanding testing principles
Applying testing techniques
What is testing?
A common misperception of testing is that it only consists of running tests.
Test activities exist before and after test execution.
Testing also includes reviewing documents and conducting static analysis.
Both dynamic testing and static testing can be used as a means for achieving similar objectives.
What are the typical objectives of testing?
To validate whether the test object is complete and works as expected.
To verify whether all specified requirements have been fulfilled.
To prevent defects.
To evaluate work products such as requirements, user stories, design, and code.
To build confidence in the level of quality of the test object.
What is the objective of component testing?
To find as many failures as possible
To increase code coverage of the component tests
To confirm that the system works as expected
To provide information to stakeholders about risks
What is the objective of acceptance testing?
To find as many failures as possible
To confirm that the system works as expected
To provide information to stakeholders about risks
To increase code coverage of the component tests
What is the difference between testing and debugging?
Testing shows failures caused by defects
Debugging finds and fixes defects
Testing is a development activity
Debugging is not related to testing
Why is rigorous testing necessary?
To reduce the risk of problems during operation
To ensure quality of components or systems
To meet contractual or legal requirements
To increase the number of defects
What may software testing be required to meet?
Contractual or legal requirements
Industry-specific standards
Both of the above
How can using appropriate test techniques affect problematic deliveries?
Increase frequency of problematic deliveries
Reduce frequency of problematic deliveries
Have no effect on deliveries
What does testing contribute to in software development?
Overall software development success
Increased defects
None of the above
What can testers involved in requirements reviews detect?
Defects
Success
None of the above
What does quality management include?
Quality assurance
Quality control
Both quality assurance and quality control
What does quality management include?
Quality assurance and quality control
Only quality assurance
Only quality control
None of the above
What is the focus of quality assurance?
Adherence to proper processes
Achieving high sales
Customer satisfaction
None of the above
What does quality control involve?
Test activities
Marketing strategies
Financial audits
None of the above
What can cause errors in a project?
Time pressure
Inexperienced participants
Miscommunication
All of the above
What can failures in a project be caused by?
Defects in the code
Environmental conditions
Both A and B
None of the above
What are the root causes of defects?
How can identifying the root causes of failure help?
Reduce the occurrence of similar defects in the future
Lead to process improvements that prevent future defects
What does testing show regarding defects?
Testing can show that defects are present
Testing can prove that there are no defects
What is said about exhaustive testing?
Test everything is feasible
Test everything is not feasible
What should be used instead of exhaustive testing?
Risk analysis and priorities
Random testing
When should testing activities start?
As early as possible in the software development life cycle
At the end of the software development life cycle
What can performing test design and review activities early do?
Find defects early when they are cheap to fix
Delay the discovery of defects
Perform the test design and review activities early can find defects early on when they are cheap to find and fix.
A small numbers of modules usually contains most of the defects discovered during pre-release testing, or is responsible for most of the operational failures.
Rule 80/20: Module core often contains 80% defects.
If the same tests are repeated over and over again, no new defects can be found.
To overcome this pesticide paradox, test cases need to be regularly reviewed and revised; new and different tests need to be written to exercise different parts of the software to find potentially more defects.
Testing is done differently in different context.
Ex: Safety-critical software is tested differently from an ecommerce site.
All specified requirements and fixing all defects found could still produce a system that is difficult to use, that does not fulfill the users’ needs and expectations, or that is inferior compared to other competing systems.
Contextual factors that influence the test process for an organization, include, but are not limited to.
Software development lifecycle model and project methodologies being used.
Test levels and test types being considered.
Product and project risks.
Business domain.
Operational constraints, including but not limited to.
Budgets and resources.
Timescales.
Complexity.
Contractual and regulatory requirements.
Organizational policies and practices.
In Agile development involves small iterations of software design, build, and test that happen on a continuous basis, supported by on-going planning. So test activities are also happening on an iterative, continuous basis within this development approach.
In sequential development, the stepped logical sequence of activities will involve overlap, combination, concurrency, or omission, so tailoring these main activities within the context of the system and the project is usually required.
Define the objectives of testing and the approach for meeting test objectives (e.g., specifying suitable test techniques and tasks, and formulating a test schedule for meeting a deadline). May be revisited based on feedback from monitoring and control activities.
Test planning
Test monitoring and control
Test analysis
Test design
Involves the on-going comparison of actual progress against the test plan using any test monitoring metrics defined in the test plan. Involves taking actions necessary to meet the objectives of the test plan.
Test planning
Test monitoring and control
Test analysis
Test execution
Analyzing the test basis appropriate to the test level being considered.
Test planning
Test monitoring and control
Test analysis
Test design
