** Lec 1 - Software testing --> Eng.

tarek roshdy**

(1) ISTQB --> Certifications ( 5 Days Crash Course ) ( unit Testing -->
Code )

(1) Quality : The sTANDARD of a certain product when compared to another

product of the same kind

Quality control ( testing ) - ( product , detect defects )

Quality Assurance - ( process , Prevent defects )

QC is part of QA

(2) Certifications ( Automotive tester )

in Egypt

CTFL ( Certified tester foundation level )

CTFL - AT ( Agile tester )
exam price 600.00 LE
i can postpone it before the exam by 7 weeks
if you didn't cancel it you will be blocked
exam is 40 question you need to solve 26 in order to
pass

(3) Error Types

error - mistake ( A problem developed by the developer )

Defect - bug -
failure (if the Bug reached the user and the
device stopped doing it job)

tester Measure the Quality not increase it.

Testing should be enough

depend on lvl of risks
technical
safety
business risks

project constrains such

as time and budget

testing shows presence of defects ( this doesn't mean that

it gets all the defects )
exhaustive testing is impossible ( you cannot test every
thing )
Early testing ( be with the process from the beginning )
Defect Clustering ( 80% - 20% theory )
pesticide paradox ( 99% theory )
testing is context Dependant ( based on the work hours
example )
 absence of error fallacy ( What you did isn't
what the client wanted )

- As a tester i have 5 main stages

1- planning and control

2- analysis and design
3- Execution and implementation
4- evaluate exit criteria (report)
5- closure activity

-Psychology of testing
( 6 - 9 Theory )
( You can look the other way and find it 9 ) " Find your own mistakes"

- Waterfall Module ( Bad , in fast small projects )

- V Module
( Business Requirement )
(Acceptance testing)

( System Requirement)
(System testing)

( High level
Design ) (integration testing )

( LowLevel Design) (unit testing)

(Coding)

- Bug life Cycle

- every req is a test condition at which i should implement some test cases

test condition is the thing i test

test case is a certain probability of the system input at which
i analysis the behavior
test cases is part of analysis and design step

pre-condition ( some thing must be done to implement my test case

)
post-condition ( some things should behave in a certain way after
my test case )

(1) title of Test( 5 - 7 words )

(1`) Description of the test if the title didnot
deliver the meaning
(2) test steps
- pre-condition
- post-condition
- assumption
- test cases
- positive test case
- negative test case
(3) expected results
(4) ID ( automatic generated )
(5) states ( pass \ fail \ blocked "Cannot test it " )

(Example 1.0)

(1) testing the find deals for any season field

pre-condition ( assuming the website is opened successfully

and the field is appeared )
post-condition ( the website should take the data and leave
a msg to me )
assumption ( the site support English language )

test cases :

( Positive cases )
(1)
Destination :
Cairo
check in :
15/3/2018
check out :
1/4/2018
2 adults , 1 child
, 2 room
leave im traveling
for work unmarked
hit search

(negative cases )

(1)
Destination :
leave it blank
check in :
15/3/2018
check out :
1/4/2018
 2 adults , 1 child
, 2 room
leave im traveling
for work unmarked
hit search

(2)
Destination :
2325
check in :
15/3/2018
check out :
1/4/2018
2 adults , 1 child
, 2 room
leave im traveling
for work unmarked
hit search
(3)
Destination :
Cairo
check in :
1/3/2018
check out :
1/4/2018
0 adults , 0 child
, 0 room
leave im traveling
for work unmarked
hit search

expected results :

( positive )

(1) the site approve the

data and get the booking page

(negative )
(1) the webpage should warn
the user to complete the required fields ( ie Destination)

states :

Bugs :

Severity : critical , major , minor

priority : High , medium , low

LEc 3 :
 TEST DESIGN TECH
Black box testing

(1) equivalence testing

- The partition theory is to test one value in each

partition (Range ) and see the system behavior.
(test cases = no.of.partition )
mainly used if the system input is
numbers

* The main defect in this system is

when the input match the condition number
(2) Boundary Value analysis testing

- the boundary theory is to test the case at which

the transition should occur and a number less than that case
Ex) if the match case occur at 5.00 ( i should
test 5.00 and 4.59 )
mainly used if the system input in
numbers and should discover the equal operator.

(3) Decision table ( kinda like truth table )

- like the equation of ( number of answer

portability ) ^ ( number of questions )
- should be used when dealing with
-
(4)state transition

- i care what your last choice is so i can test what

you need

- ATM example ( enter pass )

Correct
| |
YES NO
View option Re- Enter Pass
|
|
YES
NO
View option
return card

white box testing

(1) statement

- check the system behavior whether if he excute the

statement or not if the condition of the statement is met.
(2) decision
- check the system behavior if the condition is true
or false
experience