Test management

1. Test management
NOPRI WAHYUDI
11453105420
Program Studi S1 Sistem Informasi
Fakultas Sains dan Teknologi
Universitas Islam Negeri Sultan Syarif Kasim Riau
Pekanbaru
2017
http://sif.uin-suska.ac.id/
http://fst.uin-suska.ac.id/
http://www.uin-suska.ac.id/ Referensi Graham et.al (2006)

2. DEFINING THE SKILLS STAFF NEDD
WORKING AS A TEST LEADER
INDEPENDEN AND INTEGRATED TESTINH

3. TEST ORGANIZATION
There are many different ways to organize testing.
Traditionally we see the “project organization”, “line organization” and
“staff organization”. The modern approach to solving information
technology challenges is to have small self-contained and empowered
teams. The ultimate form, known as the “whole-team approach” or
“DevOps”, integrates all design, development, maintenance and
operations tasks. So the distinction between project organization and
line organization no longer exists. They have been blended
together. The benefits of this integrated organization are enhanced
communication and collaboration within the team, an elevation of the
various skill sets within the team to the benefit of the project, making
quality a shared responsibility. However, if your organisation has a
large number of integrated teams there will be a challenge to exchange
information about large assignments that span multiple teams

4.  People Involved
 Line managers and test managers are involved in applying the appropriate
organizational model. Everybody in the organization will be influenced by
the organizational model that is implemented.
Artifacts
 The organization of testing, as part of IT as a whole, will be described or at
least made known, to all people involved. This is closely related to the Test
Policy that could be available within the organization. Other forms could be:
 Organizational charts
 RACI matrices
 Career possibilities
 Role descriptions

5. Working as a test leader
 esponsibilities of a Test leaders tend to include involvement in the
planning, monitoring, and control of the testing activities and tasks.
 At the outset of the project, test leaders, in collaboration with the
other stakeholders, devise the test objectives, organizational test
policies, test strategies and test plans.
 They estimate the testing to be done and negotiate with
management to acquire the necessary resources.
 They recognize when test automation is appropriate and, if it is,
they plan the effort, select the tools, and ensure training of the
team. They may consult with other groups – e.g., programmers –
to help them with their testing.

6. Working as a tester
 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.

7. 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.  • 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.  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
 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.

10. Factors affecting test effort
 Testing is a complex endeavor on many projects and a variety of
factors can influence it. When creating test plans and estimating the
testing effort and schedule, you must keep these factors in mind or
your plans and estimates will deceive you at the beginning of the
project and betray you at the middle or end.
 The test strategies or approaches you pick will have a major influence
on the testing effort. This factor is so influential that we'll come back to
it in Section
 5.2.6. In this section, let's look at factors related to the product, the
process and the results of testing.
 Product factors start with the presence of sufficient project
documentation so that the testers can figure out what the system is,
how it is supposed to work and what correct behavior looks like. In
other words, adequate and high-quality information about the test
basis will help us do a better, more efficient job of defining the tests.

11.  The importance of non-functional quality characteristics such as usability,
reliability, security, performance, and so forth also influences the testing effort.
These test targets can be expensive and time consuming.
 Complexity is another major product factor. Examples of complexity consid-
erations include:
 The difficulty of comprehending and correctly handling the
problem the system is being built to solve (e.g., avionics
and oil exploration software);
 The use of innovative technologies, especially those long
on hyperbole and short on proven track records;
 The need for intricate and perhaps multiple test
configurations, especially when these rely on the timely
arrival of scarce software, hardware and other supplies;
 The prevalence of stringent security rules, strictly regimented
processes or other regulations;
 The geographical distribution of the team, especially if the team
crosses time-zones (as many outsourcing efforts do).