class 1: Software Testing Basics: Introductions

class
curriculum review

Assurance and Quality Control ? What is the difference?

Who are

you? (Software testing engineer? QA? Tester? etc.)

The Software Development team: How will you cooperate with other team players?

What is the job of a tester? What will be your responsibilities?

Qualities each software tester should possess

What is a bug (defect, issue, etc.)?

Lifecycle of a bug

verify that the software functions according to the expectations defined

by the requirements/specifications

The overall objective is not to find every software bug that exists, but to uncover situations that could negatively impact the customer, usability and/or maintainability

Software testing is a planned process that is used to identify the correctness, completeness, security and quality of software

Testing is generally done to demonstrate that the software is doing what it is supposed to do as well as the software is not doing what it is not supposed to do

planned and systematic process used to produce a quality product.
The

goal of QA is to provide assurance that a product is meeting customer’s quality expectations.
QA deals with how to prevent bugs from occurring in a product being developed.
QA is associated with activities like measuring the quality of process used to develop a product, process improvement and defect prevention.
It consists of auditing and reporting procedures related to development and testing

Control comes from the manufacturing industry where a QC inspector

would evaluate sample products taken from the manufacturing line
if the products fail the test they have the authority to shut down the production line.
QC in the software industry is used to evaluate software products, find defects & suggest improvements.
QC implements the process established by QA procedures

engineer?
QA specialist?

scripts
execute test scripts
create bug reports
report results

managers
development lead
QA lead
and possibly more

requirements for the product your team is developing
Create test scenarios.

These can be test cases, checklists, test scripts, etc.
Run and maintain test scenarios
Document the results of test scenarios after you’ve run them. (Pass or Fail)
report defects (bugs) found during run of test scenarios or any other way
Verify bug fixes

skills
good organization skills
good communication skills
good analytical skills
good technical

skills
product knowledge
end-user perspective

issue
A software bug is an error, flaw, failure or fault

in a computer program or system that produces an incorrect or unexpected result or causes it to behave in unintended ways.
Most bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code.

is a difference between the expected result and actual result
Expected

result – how we expect the software to behave
Actual results - the actual (unexpected) condition received as the result of a software test
the expected results can come from any any document describing expected behavior or look of a software, such as Business Requirements, Tech Specification, Design Guideline, etc.
the actual result is revealed during testing

tester
may be deferred
may be assigned to a developer
fixed and unit

tested by developer
re-tested by reporter
re-opened if test fails
closed if test is successful

fix

re-open

retest

close

assign

defer/decline

new/open