Intercept communication

Tools used in testing

- snoop - f=ussdb_en_1bigItem2Words.txt ; /usr/sbin/snoop -x 10.33.96.91 port 8080 | tee $f
- fiddler http://fiddler2.com/
- tcpMon
- wireShark

good practices

- emphase the relevant data:
* bold different words in repetitive items
--- habla con madre
--- habla son madre

* capitalize different letter in similar names
--- pay_wta_voms and pay_wtK_voms

- build a system to allow tracking of
* information --- in a file put the info and its source
* documentation --- use the Tracking changes
* files --- filename f=wtk_viewVoucherPrint_err379_`hostname`.txt

Isqtb . How much testing is enough?

Pressures on a project:
-time
-budget
-customer needs
Align the testing with the risks for the customers, stakeholders, project and the software

Isqtb

Fixing a bug under pressure has some chance of introduce another defect. Projects sometimes will defer fixing it.

A small number of well-placed, targeted tests may be more rigorous than a large number of badly focused tests.

It is worth learning from the problems encountered in previous projects.

Understanding the root causes- me: helps to avoid same problems and creates a thinking mechanism closer to system: how it works or how it is used.

As testers, we are also interested in looking at defects found in other projects, so that we can improve our process.

Organizations should consider testing as part of a larger quality assurance strategy.