Defining software testing

1. Defining software testing
Nama : Alfa Rizki Harahap
Nim : 11453101663
Program Studi Sistem Informasi
Fakultas Sains dan Teknologi
Universitas Islam Negeri Sultan Syarif Kasim Riau
2017

2. 1. attesting as a process

3. a. Process
 Testing is a process rather than a single activity– there
are a seriesof activities involved.

4. All life cycle activities
 looks at testing as a process that take splace
throughout the software development life cycle. We saw
earlier that the later in the life cycle we find bugs, the
more expensive they are to fix. If we can find and fix
requirements defects at the requirements stage, that must
make commercial sense. We'll build the right
software,correctly and at a lower cost over all.

5. Both static and dynamic
 that as well as tests where the software code is
executed to demonstrate the results of running tests (often
called dynamic testing) we can also test and find defects
without executing code. This is called static testing. This
testing includes reviewing of documents (including source
code) and static analysis. This is a useful and cost
effective way of testing

6. Planning
 Activities take place before and after test execution.
We need to manage the testing; for example, we plan what
we want to do; we control the test activities; we report on
testing progress and the status of the software under test;
and we finalize or close testing when a phase completes.
Chapter 5 covers these test management activities

7. Preparation
 We need to choose what testing we'll do, by selecting
test conditions and designing test cases. Chapter 4 covers
the test design activities

8. Evaluation
 As well as executing the tests, we must check the
results and evaluate the software under test and the
completion criteria, which help us decide whether we
have finished testing and whether the software product
has passed the tests.

9. Software products and related work products
 We don't just test code. We test the requirements and
design specifications, and we test related documents such
as operation, user and training material. Static and
dynamic testing are both needed to cover the range of
products we need to test.

10. 2. the reasons why we do it:

11. Determine that (software products) satisfy
specified requirements
 Determine that (software products) satisfy specified
requirements – Some ofthe testing we do is focused on
checking products against the specificationfor the product;
for example we review the design to see if it meets
requirements, and then we might execute the code to
check that it meets the design. If the product meets its
specification, we can provide that information to help
stakeholders judge the quality of the product and decide
whether it is ready for use.

12. Demonstrate that (software products) are fit for
purpose
 This is slightly different to the point above; after all
the specified requirements might be wrong or incomplete.
'Fit for purpose' looks at whether the software does
enough to help the users to carry out their tasks; we look
at whether the software does what the user might
reasonably expect. For example, we might look at who
might purchase or use the software, and check that it does
do what they expect; this might lead us to add a review of
the marketing material to our static tests, to check that
expectations of the software are properlyset. One way of
judging the quality of a product is by how fit it is for its
purpose.

13. Detect defects
 We most often think of software testing as a means of
detecting faults or defects that in operational use will
cause failures. Finding the defects helps us understand the
risks associated with putting the software into operational
use, and fixing the defects improves the quality of the
products. However, identifying defects has another
benefit. With root cause analysis, they also help us
improve the development processes and make fewer
mistakes in future work.

14.  Referensi : Graham et.al (2011)