On hard-coding of test data (2)

Posted by Albert Gareev on Jan 22, 2007
…On hard-coding of test data, continued Parameterization is a structured programming approach Starting with example. Such a function is useless when you need to sum numbers different than 2 and 3. Now let’s apply mapping. It is a little bit better, but we still have to change the source code and restart the script, if […] ...

On hard-coding of test data (1)

Posted by Albert Gareev on Jan 20, 2007
Hard-coding – storing data within the code A printed document is called “hard copy”, while its electronic version is “soft”. We can easily apply a change on a soft copy. And yet the code, compiled and assembled into an application, while stored electronically, is a “hard” copy too. Applying changes to it is almost an […] ...

On Test Data

Posted by Albert Gareev on Jan 15, 2007
Test Data should be designed. Data, that we input to application-under-test, control business logic flow. To explore every branch of the flow, we need to choose data accordingly. Wrong data trigger error-handling functionalities. To try and see all of them, we need to create data in different equivalence classes. Test Data from Production might contain non-disclosing […] ...

Link-a-log: Usability Requirements

Posted by Albert Gareev on Jan 10, 2007
Ten Usability Heuristics by Jakob Nielsen GUI Test Checklist by Barry Dorgan ...

Coined over 400 years ago

Posted by Albert Gareev on Jan 05, 2007
Why testing? Word Origin & History – by Online Etymology Dictionary late 14c., “small vessel used in assaying precious metals,” from O.Fr. test,  from L. testum  “earthen pot,” related to testa  “piece of burned clay, earthen pot, shell” (cf. L. testudo  “tortoise”) and texere  “to weave” (cf. Lith. tistas  “vessel made of willow twigs;” see […] ...
Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.