Professional Documents
Culture Documents
It8076 ST Unit Iv
It8076 ST Unit Iv
UNIT IV
TEST MANAGEMENT
People and organizational issues in testing – Organization structures for testing teams
– testing services – Test Planning – Test Plan Components – Test Plan Attachments –
Locating Test Items – test management – test process – Reporting Test Results –
Introducing the test specialist – Skills needed by a test specialist – Building a Testing Group-
The Structure of Testing Group- .The Technical Training Program
❖ This argument may have been true about twenty years ago when most of the testing was manual
and the products were somewhat simplistic.
❖ Testing stream bears a remarkable parallel to the development job functions.
❖ Requires a holistic understanding of the entire product rather than just a single module.
❖ Requires thorough understanding of the multiple domain
❖ Specialization in language
❖ Use of tools
❖ Opportunities for conceptualization and out-of the box thinking.
❖ Significant investment are made in testing today-sometimes a lot more than in development
❖ There is testing in all development and development in all testing.
❖ An internal test tool today could very well be one of those expensive test automation tools of
tomorrow.
IT8076 SOFTWARE TESTING UNIT IV
The role of the ecosystem and a call for action - Role of Education System
❖ There are formal core courses on programming but only a few universities offer core courses on
software training.
❖ Consider some of these facts about what prevails in most universities.
❖ The right values can only be more effectively caught by the students than be taught by the
teachers.
❖ There are lab courses for various development tools but non or very few for common testing tools.
IT8076 SOFTWARE TESTING UNIT IV
❖ Even during courses like operating systems and databases, the emphasis on exercises and practical
work is only on programming aspects, not on appropriately testing the built product.
❖ Most projects done as a part of the curriculum never ask for test plan nor look at testing
effectiveness.
❖ Most courses, and projects reward individual performance and present very little opportunity for
team work, which is so essential for the success of development and test engineers.
❖ Real-life scenarios like constant church of changes and the impact of such changes on quality of
the product and the demands placed on testing and quality assurance methods are seldom
emphasized.
Role of Senior Management
❖ Fairness to and recognition of testing professional should not only be done but should be seen
to be done.
❖ The senior management of organizations plays a vital role in the development of test
professionals.
❖ Some of the concrete steps they can take to achieve this are as follows
✓ Ensuring a fair distribution of appropriately talented people in the testing.
✓ Not allowing development engineers to look down upon test engineers.
✓ Encouraging and consciously ensuring that there is active job rotation
among development, testing and support functions.
✓ Demonstrating equity in recognition and reward schemes to the top performers in all
the functions, including testing.
✓ Nurturing talent in test professionals by providing them opportunities to further their
knowledge and skills.
Role of the Community
❖ As members of test community do you have pride and sense of equality? Remember authority is
taken not given.
❖ Regardless of whatever the senior management or academia do, the success of the testing
community starts from within. There are a few things that the members of the testing community,
the testing professionals should do in order to showcase and promote the testing profession .
Testers should start with a sense of pride in their job and the realization of their role in a more
holistic way, in the bigger picture of the entire product.
❖ Testers should themselves see a career in testing rather than view testing as a stop
gap arrangement or a means to get into development functions.
❖ This model, where in testing role reports to CTO and has high visibility will motivate them to
have a good target to aim for. In order to be effective
❖ The team should be small in number.
❖ It should be a team of equals or at most very few hierarchies. It should have organization with
wide representation
❖ It should have decision-making and enforcing authority and not just be a recommending
committee.
❖ A testing Services organization is made up of a number of accounts, with each account being
responsible for a major customer
❖ The account manager serves the following functions:
• Is the single point of contact between the customer and the testing services
organization for all matters and is also the point of escalation
• Developers support with the customer and is responsible for ensuring that current
projects are delivered as promised and for getting new business from the customer
• Participants in all strategic communication between the customer and the testing
services
• Acts as proxy for the customer within the testing services organization
❖ The testing services team organizes its account team as a near-site team and remote team. The
near – site team is usually a small team. It is placed at or near the customer location.
❖ This team serves the following functions:
• Be appoint of direct first point of contact for the customer for tactical or urgent
issues
• Act as a stop-gap to represent the remote team, in the event or emergencies like
travel embargo infrastructure unavailability etc.
• It also serves to increase the rapport between the customer’s operational team and
the testing services team.
IT8076 SOFTWARE TESTING UNIT IV
❖ The remote team manager manages the entire remote team and can have a peer- to –peer
relationship with the near-site team or have the near-site team reporting to him or her.
❖ All testing organizations face certain common challenges. In the case of a testing services
organization to which testing is outsourced, some of these challenges are exuberated,
primarily because of the arm’s length distance from the development team.
❖ The persons responsible for developing test plans depend on the type of plan under
development. Usually staff from one or more groups cooperates in test plan development.
❖ The type and organization of the test plan, the test plan hierarchy, and who is responsible for
development should be specified in organizational standards or software quality assurance
documents.
Introduction
❖ In this section the test planner gives an overall description of the project, the software system
being developed or maintained, and the software items and/or features to be tested. It is
useful to include a high-level description of testing goals and the testing approaches to be
used.
Items to Be Tested
❖ This is a listing of the entities to be tested and should include names, identifiers, and
version/revision numbers for each entity.
❖ The items listed could include procedures, classes, modules, libraries, subsystems, and
systems. References to the appropriate documents where these items and their behaviors are
described such as requirements and design documents, and the user manual should be
included in this component of the test plan.
❖ These references support the tester with traceability tasks.
Features to Be Tested
❖ In this component of the test plan the tester gives another view of the entities to be tested by
describing them in terms of the features they encompass. Features may be described as
distinguishing characteristics of a software component or system.
IT8076 SOFTWARE TESTING UNIT IV
Approach
❖ This section of the test plan provides broad coverage of the issues to be addressed when
testing the target software. Testing activities are described. The level of descriptive detail
should be sufficient so that the major testing tasks and task durations can be identified.
Test Deliverables
❖ Execution-based testing has a set of deliverables that includes the test plan along with its
associated test design specifications, test procedures, and test cases. The latter describe the
actual test inputs and expected outputs.
Testing Tasks
❖ In this section the test planner should identify all testing-related tasks and their dependencies.
Using a Work Breakdown Structure (WBS) is useful here. A Work Breakdown Structure is a
hierarchical or treelike representation of all the tasks that are required to complete a project.
Responsibilities
❖ The staff who will be responsible for test-related tasks should be identified. This includes
personnel who will be:
• Transmitting the software-under-test;
• Developing test design specifications, and test cases;
• Executing the tests and recording results;
• Tracking and monitoring the test efforts;
• Checking results;
• Interacting with developers;
• Managing and providing equipment;
• Developing the test harnesses; and Interacting with the users/customers.
IT8076 SOFTWARE TESTING UNIT IV
Scheduling
❖ Task durations should be established and recorded with the aid of a task networking tool.
Test milestones should be established, recorded, and scheduled.
Testing Costs
❖ The IEEE standard for test plan documentation does not include a separate cost component in
its specification of a test plan. This is the usual case for many test plans since very often test
costs are allocated in the overall project management plan. Test costs that should included in
the plan are:
• Costs of planning and designing the tests;
• Costs of acquiring the hardware and software necessary for the tests;
• Costs to support the test environment;
• Costs of executing the tests;
• Costs of recording and analyzing test results;
• Tear-down costs to restore the environment.
❖ A cost driver can be described as a process or product factor that has an impact on overall
project costs. A cost driver includes,
• Product attributes such as the required level of reliability;
• Hardware attributes such as memory constraints;
• Personnel attributes such as experience level;
• Project attributes such as use of tools and methods;
❖ Standards compromise an important part of planning in any organization standards are of two
types:
1. External standards
2. Internal standards
•External standards are standards that a product should comply with are externally
visible and are usually stipulated by external consortia.
• Internal standards are standards formulated by attesting organization to bring in
consistency and predictability.
❖ Some of the internal standards include:
• Naming and storage conventions for test artifacts
• Document standards
• Test coding standards
• Test reporting standards
❖ Easy identification of the product functionality that a set of tests are intended for
❖ Reverse mapping be identify the functionality corresponding to a given set of tests
❖ Every test artifacts have to be named appropriately and meaningfully. Such naming
conventions should enable:
Documentation standards
❖ Internal documentation of test scripts are similar to internal documentation of program code
and should include the following:
• Appropriate header level comments at the beginning of a file that outlines the
functions to be served by the test
• Sufficient in-line comments, spread throughout the file, explaining the functions
served by the various parts of a test script
• Up-to-date change history information, recording all the changes made to the test file.
Test coding standards
❖ Test coding standards go one level deeper into the tests and enforce standards on how the tests
however are written. The standards may:
• Enforce the right type of initialization and clean-up that the test should do to make the
results independent of other tests
• Encourage reusability of test artifacts
• Provide standard interfaces to external entitles like operating system, hardware and so
on.
IT8076 SOFTWARE TESTING UNIT IV
❖ The test plan and its attachments are test-related documents that are prepared prior to test
execution. There are additional documents related to testing that are prepared during and after
execution of the tests.
Test Log
❖ The test log should be prepared by the person executing the tests. It is a diary of the events that
take place during the test. It supports the concept of a test as a repeatable experiment. The test
log is invaluable for use in defect repair . It gives the developer a snapshot of the events
associated with a failure. Retest that follows defect repair is also supported by the test log.
❖ The test log is valuable for regression testing that takes place in the development of future
releases of a software product , and circumstances where code from a reuse library is to be
reused . The test log can have many formats . An organization can design its own format or
adopt IEEE recommendations.
Description
❖ In the description section the tester should identify the items being tested , their version /
revision number , and their associated Test Item /Transmittal Report . The environment in
which the test is conducted should be described including hardware and operating system
details.
Activity and Event Entries
❖ The tester should provide dates and names of test log authors for each event and activity. This
section should also contain:
• Execution description
• Procedure results
• Environmental information
• Anomalous events
• Incident report identifiers
IT8076 SOFTWARE TESTING UNIT IV
QUESTION BANK
PART-A
2. What are the possibilities available for organizing a testing team in multi-product company?
❖ A central “test think-tank/brain trust” team, which formulates the test strategy for the
organization.
❖ One test team for all the products.
❖ Different test team for each product [or related product]
❖ Different test teams for different types of tests.
❖ A hybrid of all the above models.
Testing Services
Test Planning
4. What is plan?
A plan is a document that provides a framework or approach for achieving a set of goals. Test plans
tend to be more technically oriented. However, a software project plan that may contain a test plan as well will
often refer to business goals.
5. What is milestone?
Milestones are tangible events that are expected to occur at a certain time in the project’s lifetime.
Managers use them to determine project status.
IT8076 SOFTWARE TESTING UNIT IV
7. What are the test costs that should be included in the test plan?
❖ Costs Of Planning And Designing The Tests;
❖ Costs Of Acquiring The Hardware And Software Necessary For The Tests (Includes
Development Of The Test Harnesses);
❖ Costs To Support The Test Environment;
❖ Costs Of Executing The Tests;
❖ Costs Of Recording And Analyzing Test Results;
❖ Tear-Down Costs To Restore The Environment.
❖ Testing costs
❖ Approvals
11. Define Suspension & Resumption criteria.
The criteria to suspend and resume testing are described in the simplest of cases testing is suspended
at the end of a working day and resumed the following morning.
18. What is the purpose of test transmitted report and test log? [Nov 2012]
Suppose a tester is ready to run on the data described in the test plan. We need to be able to locale the
item and have knowledge of its current status. This is the function of the test transmitted report.
The test log should be prepared by the person executing the tests. It is a diary of the events that take
place during the test. It supports the concept of a test as a repeatable experiment.
19. List out the information that should be included in test transmittal report.
Each Test Item Transmittal Report has a unique identifier. It should contain the following information for
each item that is tracked.
(i) version/revision number of the item;
(ii) location of the item;
(iii) persons responsible for the item (e.g., the developer);
(iv) references to item documentation and the test plan it is related to;
(v) status of the item;
(vi) approvals—space for signatures of staff who approve the transmittal.
Test Management
20. What are the types of standards used for managing the test process?
❖ Internal standards
❖ External standards
Test Process
21. What are activities /processes involved in testing?
❖ Putting together and base lining a test plan
❖ Test case specification
❖ Update of traceability matrix
❖ Identifying possible candidates for automation
❖ Developing and base lining test cases
❖ Executing test cases and keeping traceability matrix current
❖ Collecting and analyzing metrics
❖ Preparing test summary report
❖ Recommending product release criteria
29. What are the skills needed for tester on personal managerial level?[Nov 2014] [Nov 2016]
❖ Organizational, And Planning Skills;
❖ The Ability To Keep Track Of, And Pay Attention To, Details;
❖ The Determination To Discover And Solve Problems;
❖ The Ability To Work With Others And Be Able To Resolve Conflicts;
❖ The Ability To Mentor And Train Others
30. What are the skills needed for a test specialist?[CS1016-Nov 2014] [ Nov 2017]
❖ Strong Coding Skills And An Understanding Of Code Structure And Behaviour
❖ A Good Understanding Of Testing Principles And Practices
❖ A Good Understanding Of Basic Testing Strategies, Methods, And Techniques
PART B
1. Explain issues caused by people and organization in software testing. [Nov 2014 – 8M]
[Nov 2009-8M] [Refer Pg.no:125]
2. Briefly discuss the testing team in organizational structures. [ Nov 2014-8M] [Refer Pg.no:128]
3. Explain the role of testing. [Nov 2009- 8 M] [Refer Pg.no:131]
4. State and discuss the various stages of a test plan [Nov 2009 – 8M] [Refer Pg.no:132]
5. Explain about test plan components. (Or) What are some of the essential items a tester should
include in a test plan? [CS1016-Nov 2014-8M] [ Nov 2017-16M] [Refer Pg.no:133]
6. Describe test related documents that are developed during and after execution based testing.
[ Nov 2014 – 8M][May 2017] [Refer Pg.no:136]
7. Write short notes on locating test items. [4M] [Refer Pg.no:137]
8. Write a short note on test management. [8M] [Refer Pg.no:138]
9. Explain the testing process in detail. [8M] [Refer Pg.no:140]
10. Write short notes on test report. [8M] [Refer Pg.no:142]
11. Briefly discuss the various groups in Test Plan and policy development with their role.
[ Nov 2014-16M] [Refer Pg.no:144]
12. Write short note on test specialist. [6M] [Refer Pg.no:145]
13. Explain the skills needed by attest specialist. [May 2017-16M] [ Nov 2017-8M] [Refer Pg.no:146]
14. How can we build a test group? [Nov 2009 -8M] [ Nov 2017-8M] [Refer Pg.no:147]