Browse Prior Art Database

Parallel Development Parallel Automation (PDPA) -a kind of Agility Automation Tool helps to write automation code from manual test cases with parallel to application feature development automatically.

IP.com Disclosure Number: IPCOM000255768D
Publication Date: 2018-Oct-12
Document File: 3 page(s) / 271K

Publishing Venue

The IP.com Prior Art Database

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 55% of the total text.

Parallel Development Parallel Automation (PDPA) -a kind of Agility Automation

Tool helps to write automation code from manual test cases with parallel to

application feature development automatically.

Background

Problem 1: How to achieve quality testing and development in same development

cycle? So we can save extra testing time post development.

Problem 2: How to convert manual test cases to automation script for carry forwarding

quick test execution immediately post development without having a standard delay of

preparing only test cases?

Ans: I have created an eclipse plugin that helps the available resource to start writing

test cases (as requirement validation) in a plain readable text format parallel to

development activity by looking to mock-up. Then convert the manual test cases to

automation script in a fraction of seconds where the candidate can finish the

concreteness of the scripts quickly and place in a pipeline for its execution and

validation once the feature development is ready and released.

It helps the team not to waste the precious time, waiting for completion of development

of an application feature, by carry forwarding testing after development. This approach

is "Parallel Development Parallel Testing (PDPT)"

Problem 3: How to get complete details of test cases (UI, Rest, DB or Unit etc.) are

validated over the application feature post its execution automatically.

Ans: It helps to execute the test cases (ID + Description) mentioned in the text file in

sequence and generates the report accordingly post execution. So, the report is

generated with Test ID + Test Description marking different color for different status

through a third-party tool.

Problem 4: The drawbacks of third-party tool is it doesn't allow auto converting manual

test cases to automation test scripts. It only follows the traditional testing approach of

"First Development Last Testing (FDLT)".

Problem 5: Achieving Globalization Testing without touching the real test code?

Ans: It also helps to add different language texts in xml file or in database to validate

over the UI once the feature/element is ready.

3. Summary

This automation framework can easily be adopted in a in Agile project development.

There is already availability of many BDD (Behavior Driven Development) framework

that too helps to start writing manual business requirements or behaviors in s...