Unit-IV; Professional Sales Representative (PSR).pptx
Test management
1. Test Management
Emi Rizki Ayunanda
11453201739
Sistem Informasi
Fakultas Sains Dan Teknologi
Universitas Islam Negeri Sultan Syarif Kasim Riau
Oleh :
2. TEST ORGANIZATION
In this section, let's talk about organizing a test effort
within a project. We'll look at the value of independent testing, and
discuss the potential benefits and risks associated with
independent testing. We will examine the various types of different
test team members we might want on a test team. And we'll
familiarize ourselves with the typical tasks performed by test
leaders and testers.
As we go through this section, keep your eyes open for
the glossary terms tester, test leader and test manager.
3. TEST
ORGANIZATION
The approaches to organizing a test team vary, as
do the places in the organ- ization structure where the test
team fits. Since testing is an assessment of quality, and
since that assessment is not always positive, many
organizations strive to create an organizational climate
where testers can deliver an inde- pendent, objective
assessment of quality.
When thinking about how independent the test
team is, recognize that inde- pendence is not an either/or
condition, but a continuum. At one end of the continuum lies
the absence of independence, where the programmer
performs testing within the programming team.
1) Independent and Integrated Testing
4. TEST
ORGANIZATION
Moving toward independence, you find an integrated
tester or group of testers working alongside the programmers, but
still within and reporting to the development manager. You might
find a team of testers who are independ- ent and outside the
development team, but reporting to project management.
Near the other end of the continuum lies complete independence.
You might see a separate test team reporting into the
organization at a point equal to the development or project team.
You might find specialists in the business domain (such as users
of the system), specialists in technology (such as data- base
experts), and specialists in testing (such as security testers,
certification testers, or test automation experts) in a separate test
team, as part of a larger independent test team, or as part of a
contract, outsourced test team. Let's examine the potential
benefits and risks of independence, starting with the benefits.
1) Independent and Integrated Testing
5. 2) Working as a test leader
We have seen that the location of a test team
within a project organization can vary widely. Similarly there
is wide variation in the roles that people within the test team
play. Some of these roles occur frequently, some
infrequently. Two roles that are found within many test teams
are those of the test leader and the tester, though the same
people may play both roles at various points during the
project. Let's take a look at the work done in these roles,
starting with the test leader.
6. TEST
ORGANIZATION
As with test leaders, projects should include testers at
the outset, though it is often the case that project doesn't need a
full complement of testers until the test execution period. In the
planning and preparation phases of the testing, testers should
review and contribute to test plans, as well as analyzing, review-
ing and assessing requirements and design specifications. They
may be involved in or even be the primary people identifying test
conditions and cre- ating test designs, test cases, test procedure
specifications and test data, and may automate or help to
automate the tests. They often set up the test envi- ronments or
assist system administration and network management staff in
doing so.
3) Working as a tester
7. 4) Defining the skills test staff need
Doing testing properly requires more than defining
the right positions and number of people for those positions.
Good test teams have the right mix of skills based on the
tasks and activities they need to carry out, and people
outside the test team who are in charge of test tasks need the
right skills, too. People involved in testing need basic
professional and social qualifications such as literacy, the
ability to prepare and deliver written and verbal reports, the
ability to communicate effectively, and so on. Going beyond
that, when we think of the skills that testers need, three main
areas come to mind:
8. 4) Defining the skills test staff need
Application or business domain: A tester must understand
the intended behavior, the problem the system will solve,
the process it will automate and so forth, in order to spot
improper behavior while testing and recognize the 'must
work' functions and features.
Technology: A tester must be aware of issues, limitations
and capabilities of the chosen implementation technology,
in order to effectively and effi ciently locate problems and
recognize the 'likely to fail' functions and features.
Testing: A tester must know the testing topics discussed
in this book - and often more advanced testing topics - in
order to effectively and efficiently carry out the test tasks
assigned.
9. 4) Defining the skills test staff need
The specific skills in each area and the level of
skill required vary by project, organization, application, and
the risks involved.
The set of testing tasks and activities are many
and varied, and so too are the skills required, so we often see
specialization of skills and separation of roles. For example,
due to the special knowledge required in the areas of testing,
technology and business domain, respectively, test tool
experts may handle automating the regression tests,
programmers may perform compo- nent and integration tests
and users and operators may be involved in acceptance
tests.
10. 4) Defining the skills test staff need
We have long advocated pervasive testing, the
involvement of people throughout the project team in carrying
out testing tasks. Let us close this section, though, on a
cautionary note. Software and system companies (e.g.,
producers of shrink-wrapped software and consumer
products) typi- cally overestimate the technology knowledge
required to be an effective tester. Businesses that use
information technology (e.g., banks and insur- ance
companies) typically overestimate the business domain
knowledge needed.
11. 4) Defining the skills test staff need
All types of projects tend to underestimate the
testing knowledge required. We have seen a project fail in
part because people without proper testing skills tested
critical components, leading to the disastrous discovery of
fundamental architectural problems later. Most projects can
benefit from the participation of professional testers, as
amateur testing alone will usually not suffice.
