Automate at the feature levelpushthe Automate at the storytests levellower Automate at the task level
Tests / Examples passes toAPI teststructure Test Method / Fixture calls Developer CodeCopyright 2012DragonFire Inc.
TestLogIn test / examplesUser Name Password Expected result commentsJanetGregory Password Access system as JanetGregory Valid combo savedJanet Gregory Password Error Space in user name boolean TestLogIn (userName, password, expected result) call LogIn (userName, password) compare (actual result, expected result) if true, return pass test method else / fixture return fail end boolean LogIn (name,pwd) Developer code stuff ……….. code if logged in, return true else return false Copyright 2012 DragonFire Inc. end
• enables testers / • tests are usually business to define tests through the UI• test code can be in • programmers aren’t programming language usually willing to help• programmers can run • tests are implemented tests as they code after the code is written• testers can ask • testers create and programmers for help implement all tests• takes time from ‘coding’ production codeCopyright 2012DragonFire Inc. 9
• less abstraction between layers ◦ presentation vs. business layer • more logic in the GUI layer • where is the separation in tests? • who does what?Copyright 2012DragonFire Inc. 10
So, if we can’t test all (most) functionality at the API layer ... Any stories to share?Copyright 2012DragonFire Inc. 12
two big questions .... Do testers need to know how to code? Can programmers do all the testing? 14
• system architecture ◦ high level (context) ◦ component levelThx to Lynn McKee for the term technical awareness 15