As you build out your presentation, here are a few dos and don’ts.
This is where CA Test Data Management Solution comes into play. It simplifies the entire test process from test design to on-demand data access for testers.
In June 2015 CA completed its acquisition of Grid Tools.
Gets the data and/or defines the data that will be generated
Automatically match fit for purpose data to the minimum number of tests, cover 100% of requirements in the smallest number of tests
Visualize the test data, identifying the white spaces in test data and identify data that will need to be generated to fill the white space.
Identify trends within your data, and assess the impact of future trends
Data Masking we have two different masking options
Fast Data Masking - Native Database Connections – fast, masked views and shadow tables
Simple Data Masking - Generic Connectors
Synthesizing
Fill in data gaps
Create sets of “bug” data
Masking enables compliance, but synthetic data ensures it
Enhance legacy data using synthetic data creation
Test Data on Demand - Test Data on Demand is a self-service, web portal that sits on top of the Test Data Warehouse. Centralizing data requests and removing data dependencies lets you reduce the time to provision consistent, rich sets of intelligent data by 50%. Data can also be linked directly to test cases and re-used and shared across multiple teams, in parallel, to remove the constraints of cross-system dependencies on testing.
Test Case Optimizer
Is a business process modeling tool/Flowchart modeling tool.
It allows us to take a business process and graphically formalize the requirements, test cases and even data in one tool.
It makes requirements very clear and unambigious it is hard to misinterpret the requirements.
Here is a simple example
This is a process of making a cup of tea In this simple example you can see different decision points and different paths it can take.
If you are doing this manually it is going to be very hard to tell the number of test cases you need to cover all the paths.
That is where TCO comes and it can tell you exactly how many test cases you need to get optimum coverage.
It really improves the quality of your requirements and test cases
It allows us to analyze and optimize the test cases.
Agile Designer™ will increase your functional coverage in minutes by detecting the smallest number of test cases that have the maximum coverage. Agile Designer™ will also remove any duplicate, invalid or redundant test cases to avoid test teams over testing the same functionality. Performing fewer test cases of a higher quality means that test cycles will be shortened and the cost of testing reduced, without compromising the quality of the software.
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.