Small is Beautiful- Fully Automate your Test Case Design

Manager Product Marketing at CA Technologies em CA Technologies
19 de Mar de 2015
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
Small is Beautiful- Fully Automate your Test Case Design
1 de 30

Mais conteúdo relacionado

Mais procurados

Kanban like another approach for gaming projects, Катерина ГаськоваKanban like another approach for gaming projects, Катерина Гаськова
Kanban like another approach for gaming projects, Катерина ГаськоваSigma Software
 Guidelines to Measuring Test Automation ROI Guidelines to Measuring Test Automation ROI
Guidelines to Measuring Test Automation ROIPerfecto by Perforce
6 Traits of a Successful Test Automation Architecture6 Traits of a Successful Test Automation Architecture
6 Traits of a Successful Test Automation ArchitectureErdem YILDIRIM
Testing automation in agile environmentTesting automation in agile environment
Testing automation in agile environmentPerfecto Mobile
Test Automation Strategies For AgileTest Automation Strategies For Agile
Test Automation Strategies For AgileNaresh Jain
Developing a test automation strategy by Brian BayerDeveloping a test automation strategy by Brian Bayer
Developing a test automation strategy by Brian BayerQA or the Highway

Similar a Small is Beautiful- Fully Automate your Test Case Design

Load testing with Visual Studio and Azure - Andrew SiemerLoad testing with Visual Studio and Azure - Andrew Siemer
Load testing with Visual Studio and Azure - Andrew SiemerAndrew Siemer
How To Transform the Manual Testing Process to Incorporate Test AutomationHow To Transform the Manual Testing Process to Incorporate Test Automation
How To Transform the Manual Testing Process to Incorporate Test AutomationRanorex
SCRIMPS-STD: Test Automation Design Principles - and asking the right questions!SCRIMPS-STD: Test Automation Design Principles - and asking the right questions!
SCRIMPS-STD: Test Automation Design Principles - and asking the right questions!Richard Robinson
TEST_AUTOMATION_CASE_STUDY_(2)2[1]TEST_AUTOMATION_CASE_STUDY_(2)2[1]
TEST_AUTOMATION_CASE_STUDY_(2)2[1]Clive Dall
Aligning Software Testing With Modern Age Development PracticesAligning Software Testing With Modern Age Development Practices
Aligning Software Testing With Modern Age Development PracticesAspire Systems
Questions for successful test automation projectsQuestions for successful test automation projects
Questions for successful test automation projectsDaniel Ionita

Similar a Small is Beautiful- Fully Automate your Test Case Design(20)

Último

The Never Landing Stream with HTAP and StreamingThe Never Landing Stream with HTAP and Streaming
The Never Landing Stream with HTAP and StreamingTimothy Spann
Workflow Engines & Event Streaming Brokers - Can they work together? [Current...Workflow Engines & Event Streaming Brokers - Can they work together? [Current...
Workflow Engines & Event Streaming Brokers - Can they work together? [Current...Natan Silnitsky
Endlich gute API Tests. Boldly Testing APIs Where No One Has Tested Before.Endlich gute API Tests. Boldly Testing APIs Where No One Has Tested Before.
Endlich gute API Tests. Boldly Testing APIs Where No One Has Tested Before.QAware GmbH
baklink.docxbaklink.docx
baklink.docxAbdAsisHusainSalam
Expo - Zero to App.pptxExpo - Zero to App.pptx
Expo - Zero to App.pptx😎 Anthony Kariuki
The Pharo Debugger and Debugging tools: Advances and RoadmapThe Pharo Debugger and Debugging tools: Advances and Roadmap
The Pharo Debugger and Debugging tools: Advances and RoadmapESUG

Último(20)

Small is Beautiful- Fully Automate your Test Case Design

Notas do Editor

  1. Even with what looks like a very simple requirement there are a large number of potential use cases. In this example the complexity comes from the reset button.
  2. Point One: generate the perfect set of test cases directly from the requirements From the requirements flowchart, Agile Designer will identify every possible path through the system. Where it gets clever is the path optimization. This uses “deep, dark maths” to identify the smallest number of paths needed to fully test a systems functionality – i.e., to fully test the requirements now that they are fully defined. Users can choose from multiple algorithms, to automatically generate the smallest number of test cases to cover: all possible paths; all edges (arrows in/out of the blocks); all nodes; all in/out edges; all pairs. Automatically generating test cases removes testing bottlenecks: Manually writing test cases and test scripts is slow and error-prone (i.e., it provides poor coverage) For example: 6 hours to produce 11 test cases with 16% coverage (internal) Testing currently takes up around 47% of the SDLC. Path explorer – Look at all possible paths through the functional logic of the flowchart Identify the smallest number of test cases needed to test maximum functionality Store/create your test cases (use cases) Store these test cases – push them out to automation engines, ALM/QC etc. In the path explorer: go to your test cases, and click ‘export special’. Select which folder you want to save them in. Update and add new test cases. Point two: maximum coverage means you can test more for less Agile Designer helps reduce testing time and costs by identifying the smallest number of tests needed. This means that you can systematically improve coverage, knowing that all requirements have been tested. This is in contrast to industry standard, where much testing is redundant, and much functionality goes untested: Over-testing of certain functions by 40 times Typically only 10-20% coverage – negative/unhappy paths go untested Up to 30% of testing time is wasted on duplicate, invalid or redundant tests Examples of optimization: A financial services company created 11 test cases in 6 hours with 16% requirement coverage Agile Designer automatically created 17 test cases in 2 hours with 100% coverage Another project relied on 3 test cases which provided just 5% coverage, this resulted in bugs making it into production which is expensive to fix Agile Designer generated 12 test cases with 100% coverage in 30 minutes In one project, the possible number of cases identified was 326; Agile Designer identified that only 17 were needed for 100% coverage Point Three: The same algorithms used to identify the test cases can be used assess how much functional coverage the stored test cases provide. The notion of perfect test cases is based on the concept of coverage, path modelling and risk-based testing.
  3. From these test cases…The secret of Agile Designer is that by doing one thing you create multiple outputs, for example by designing the perfect set of test cases you are creating a static test of the requirements document. You can push out Story boards Complexity analysis – how long should this take? Virtualization end points Test Data Automation scripts AND even push actions, use cases and test cases to story boards From a flowchart, you therefore have all the qualitative information needed to work through the development lifecycle, up to the execution of automation scripts. Once you have stored your paths, you simply have to push them back to TMX. From there, you can use them in your automation engine of choice, automatically testing an application iteratively. Typically the BA writes the requirement along with a few diagrams. There are usually lots of words. These have to be interpreted by the programmer and then by the tester. These words (based on each users local domain knowledge and location) are often ambiguous and result in the wrong thing being developed or tested. Even harder are change requests, the amount of work for a simple change request is massive as all existing test cases have to be verified and changed again, and test scripts have to be rewritten. With Agile Designer the hard work is concentrated in the requirements gathering stage – all the hard work is concentrated here.