Posted by Albert Gareev on Jun 04, 2009
Original date: 30 Mar 2009, 1:30pm Front-End Test Automation Practices – Model-based Hybrid Keyword/Data Driven Framework 1. Description • Framework creation – Pure programmatically • Test creation – scriptless, visual design • Internal Data Model, capable to import/export data from various sources • GUI/Database checkpoints, parameterized/transitioned • Business Verification Rules • Framework-based structure; ...
Posted by Albert Gareev on Jun 02, 2009
Original date: 19 Mar 2009, 1:30pm Front-End Test Automation Practices – Keyword-Driven Framework 1. Description • Framework and keywords creation – programmatically • Tests creation – table editor (common practice – MS Excel) • Parameterized, capable to import spreadsheets • GUI/Database checkpoints, hard-coded and/or parameterized • Framework-based structure • Limited error handling • Keyword-based flow ...
Posted by Albert Gareev on Jun 01, 2009
Original date: 11 Mar 2009, 1:30pm Front-End Test Automation Practices – Data-Driven Framework 1. Description • Programmatically created • Parameterized, capable to import spreadsheets • GUI/Database checkpoints, hard-coded and/or parameterized • Library-based structure • Possibly error handling • Hard-coded yet data-driven flow (input and logic) • Standard reporting • Verification is limited to Testing Tool’s […] ...
Posted by Albert Gareev on May 31, 2009
Original date: 3 Mar 2009, 1:00pm Front-End Test Automation Practices – Record/Playback Enhanced 1. Description • Parameterized data • Dataset is a part of the script but not in the code • Verification via GUI checkpoints (hard-coded) • Hard-coded flow • No error handling • No or limited reporting • No structure 2. Advantages • […] ...
Posted by Albert Gareev on May 30, 2009
Original date: 26 Feb 2009, 1:00pm Front-End Test Automation Practices – Record/Playback 1. Description • Hard-coded data • Hard-coded flow • No error handling • No or limited reporting • No structure • No verification • No validation 2. Advantages • Easy to create • Quick to create • No programming required 3. Disadvantages • […] ...
Posted by Albert Gareev on Oct 10, 2008
For Test Automation, Functional Decomposition is a test flow analysis and test design technique. And yet somehow it is often confused with structural programming. Decomposition of Test Flow Applying Functional Decomposition technique in Test Flow Analysis means splitting (decomposing) a testing scenario into its constituent parts, that are logically complete and data-wise isolated. Some of these parts […] ...
Posted by Albert Gareev on May 15, 2007
What’s it about? Automated tests represent a certain test logic as a sequence of steps, manipulating data and interacting with a GUI. Test data, as in manual testing, could be data we feed into application-under-test (input data), retrieve from application-under-test (actual data, or actual result), and compare with (expected result). These data have to be […] ...
