ISTQB Foundation Level Exam Crash Course Part-24
This is Part 24 of 35 containing 5 Questions (Q. 116 to 120) with detailed explanation as expected in ISTQB Foundation Level Exam Latest Syllabus updated in 2011
Deep study of these 175 questions shall be of great help in getting success in ISTQB Foundation Level Exam
Q. 116: What are the various Pros & Cons of Implementing Independent Testing?
Independence in the implementation of testing has some key benefits and drawbacks, as described in the following table.
|
|
||
|
Sr. |
Benefits |
Drawbacks |
| 1 | The tester sees other and different defects to the author | Isolation from the development team (if treated as totally independent), which will mean the tester is totally dependent on the test basis to understand what it is the tester is testing (documentation that is rarely up to date) |
| 2 | The tester is unbiased | The tester may be seen as the bottleneck, as independent test execution is normally the last stage and affected by any delays earlier in the process |
| 3 | The tester can see what has been built rather than what the developer thought had been built | Developers lose a sense of responsibility for quality as it may be assumed that they need not worry about errors because the independent test team will find them |
| 4 | The tester makes no assumptions regarding quality | The fully independent view sets developers and testers on either side of an invisible fence. This can be a hindrance to communication that would in normal circumstances ensure common understanding and effective working. It can also mean that developers are seen to �throw� the software over the fence |
<<<<<< =================== >>>>>>
Q. 117: Testing can be done by which type of people?
Testing tasks are traditionally carried out by people who make testing a career; however, testing tasks may also be carried out by non-testers such as a project manager, quality manager, developer, business and domain expert, infrastructure or IT operations.
The availability of resources usually determines the resource types that are deployed on each project, e.g. if there are no career testers available an organization may identify non-testing IT or business resources to carry out the role of tester for a specific project or time period.
The syllabus defines two testing roles, the test leader (or test manager/test coordinator) and the tester.
<<<<<< =================== >>>>>>
Q. 118: what is the difference between a testing role and a testing job?
There is great difference between a testing role and a testing job.
A role is an activity, or a series of activities given to a person to fulfil, e.g. the role of test leader. A person may therefore have more than one role at any moment depending on their experience and the level of workload on a project.
A job is effectively what an individual is employed to do, so one or many roles could make up a job. For example, a test leader could also be a tester.
<<<<<< =================== >>>>>>
Q. 119: What are the tasks undertaken by a test leader?
The tasks undertaken by a test leader align very closely with those undertaken by a project manager and align closely with standard approaches to project management. In this context a test leader is anyone who leads a team of testers. They are also known as test program managers, test managers, test team leaders and test coordinators.
Typical test leader tasks may include:
1) Coordinating the development of the test strategy and plan with project managers and others.
2) Writing or reviewing test strategies produced for the project, and test policies produced for the organization.
3) Contributing the testing perspective to other project activities, such as development delivery schedules.
4) Planning the development of the required tests – which will include ensuring that the development uses the correct understanding of the risks, selecting the required test approaches (test levels, cycles, approach, objectives and incident management planning), estimating the time and effort and converting to the cost of testing and acquiring the right resources.
5) Managing the specification, preparation, implementation and execution of tests, including the monitoring and control of all the specification and execution.
6) Taking the required action, including adapting the planning, based on test results and progress (sometimes documented in status reports), and any action necessary to compensate for problems or delays.
7) Ensuring that adequate configuration management of testware is in place and that the testware is fully traceable, e.g. there is a hierarchical relationship established between the requirements and the detailed specification documents.
8) Putting in place suitable metrics for measuring test progress and evaluating the quality of the testing delivered and the product.
9) Agreeing what should be automated, to what degree, and how, ensuring it is implemented as planned.
10) Where required, selecting tools to support testing and ensuring any tool training requirements are met.
11) Agreeing the structure and implementation of the test environment.
12) Scheduling all testing activity.
13) At the end of the project, writing a test summary report based on the information gathered during testing.
<<<<<< =================== >>>>>>
Q. 120: What are the tasks undertaken by a tester?
Generally a tester is also known as test analyst or test executor.
The tasks typically undertaken by a tester may include:
1) Reviewing and contributing to the development of test plans.
2) Analyzing, reviewing and assessing user requirements, specifications and models for testability.
3) Creating test specifications from the test basis.
4) Setting up the test environment (often coordinating with system administration and network management). In some organizations the setting up and management of the test environment could be centrally controlled; in this situation a tester would directly do liaison with the environment management to ensure the test environment is delivered on time and to specification.
5) Preparing and acquiring/copying/creating test data.
6) Implementing tests on all test levels, executing and logging the tests, evaluating the results and documenting the deviations from expected results as defects.
7) Using test administration or management and test monitoring tools as required.
8) Automating tests that may be supported by a developer or a test automation expert.
9) Where required, running the tests and measuring the performance of components and systems.
10) Reviewing tests developed by other testers.
Part – 25 of the Crash Course – ISTQB Foundation Exam
Access The Full Database of Crash Course Questions for ISTQB Foundation Level Certification
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.
Thank God! Someone with brnias speaks!