What’s new in version 3.1
New BizDataX version announced at the Swiss Testing Day 2016 in Zürich (Switzerland) introduces the Test Data Self Service portal and a number of improvements related to all three key BizDataX components.
Test Data Self Service portal is specifically designed with the testers in mind. Testers are constantly in the need for the relevant test data for their test cases and invest (to be more precise, waste) a significant part of their time to search for relevant test data or create test data or, even worse, execute test cases with the wrong test data. Test Data Self Service portal enables testers to define test cases they need relevant test data for, acquire new test data for the test cases, reserve test data, mark test data as ‘used’ and delete test data.
Here is the basic usage scenario:
- Tester defines or imports test cases from various test management tools.
- Test data producer implements workflow that delivers test data for the specified test case(s).
- Database administrator executes the workflow.
- Tester gets notified about successful workflow execution.
- Tester acquires a designated number of test data records for each test case.
- Tester can reserve particular test data (so other testers cannot to use it).
- Tester can mark test data as ‘used’, notifying others that the test data cannot be used again (i.e. test data is not relevant for the specified test case any more).
- Tester can delete test data that is no longer needed.
- When more test data is needed, tester notifies the administrator to re-execute the workflow and produce new data.
Data processing redesigned
Improved support for (anonymization during) ETL, i.e. read from CSV file and write into relation database while subsetting and masking data on the way.
Extensible architecture is introduced for handling various data access technologies, additional handlers ship as add-on packages via NuGet Package Manager (see image below).
Due to its design and flexibility in workflow implementation, performance has always been a strength of BizDataX. We went a step further by enabling users to setup batch size and number of worker threads per iterator when writing in the data store (see image below). BizDataX Runtime also enables parallel workflow execution from multiple hosts, i.e. scaling-out.
In complex data transformation scenarios, users create large workflows consisting of hundreds of data transformation rules. BizDataX Designer enables users to store workflows in arbitrary number of files supporting better workflow management, visibility and reusability
Lookup data (Catalogs) improved
Lists of names, cities and streets for more countries added.
Extensibility mechanisms introduced, register custom lookup providers and lookup items.
Handling and logging of errors and warnings improved, architecture changed to support a variety of output targets and to support selective control which log statements are output at arbitrary granularity.
Integration between BizDataX Portal and Designer
Testers, test managers, test data producers and other roles need to exchange project relevant data in order to complete efficiently their tasks. To support this, Portal data like project policies and test case definitions can be imported to Designer to enable test data producers to implement adequate workflows. For more clarity and transparency, policies can be added to the workflow as containers containing the data transformation logic they refer to.
Many Designer toolbox activities have been improved in terms of usability and performance. There have been some security improvements (more security roles involved) and improvements in the sensitive data discovery module.