This Research Paper proposed an approach to generate test cases in which requirements with different

types are covered. The proposed approach uses text mining and symbolic execution methodology for
test data generation and validation, where a knowledge base is developed for multi-disciplinary
domains.

We move to the test automation to minimize human effort and cost to fix bugs and errors, as well as to
improve the quality of the testing process by automating it. In case of test automation, if the process is
carried out at early phase of the development life cycle, it saves more time and effort to detect errors.
At later stages, enormous errors would be generated as soon as the code is completed, where it
demands a lot of code correction and modification.

In waterfall models, testing is conducted when we get an executable software. In contrast, under an
agile approach, requirements, programming, and testing are often done concurrently. For Waterfall
models, test cases can be generated from functional and non-functional requirements. While in agile
models, user stories are investigated to generate test cases.

We propose an automated test case generation approach to generate test cases from requirements.
Test cases can be generated either from agile or waterfall models. For agile models, user stories of a
release are used to generate test cases. While in waterfall models requirements can be represented in
different forms (functional, non-functional and use-case models).

Now we will see how this solution works? It starts by checking model, if model is agile, the stories are
parsed, clustered by sprints then test paths are generated. After optimizing these test paths optimized
test paths are generated. And at last, test data is generated and validated. If model is waterfall srs
document is parsed then use case model is used for further processing as previously described but for
functional and non-functional requirements text minor technique is used to detect verbs and these
verbs are stored in knowledge base. Then After performing symbolic execution test cases are validated.

In conclusion, the proposed approach proves efficiency where the effort required for generating a test
case decreases after optimization than that before optimization due to increasing the number of
generated test cases.

This Research Paper proposed an approach to generate test cases in which

requirements with different types are covered.
We move to the test automation to minimize human effort and cost to fix bugs
and errors, as well as to improve the quality of the testing process by
automating it. For Waterfall models, test cases can be generated from
functional and non-functional requirements. While in agile models, user stories
are investigated to generate test cases.
We propose an automated test case generation approach to generate test
cases from requirements. Test cases can be generated either from agile or
waterfall models. For agile models, user stories of a release are used to
generate test cases. It starts by checking model, if model is agile, the stories
are parsed, clustered by sprints then test paths are generated. After
optimizing these test paths optimized test paths are generated. If model is
waterfall srs document is parsed then use case model is used for further
processing as previously described but for functional and non-functional
requirements text minor technique is used to detect verbs and these verbs are
stored in knowledge base.
In conclusion, the proposed approach proves efficiency where the effort
required for generating a test case decreases after optimization than that
before optimization due to increasing the number of generated test cases.

This research paper proposed Use Case Modelling for System Tests Generation (UMTG), an approach
that automatically generates executable system test cases from use case specifications and a domain
model. To extract behavioral information from use cases and enable test automation, UMTG employs
Natural Language Processing (NLP), a restricted form of use case specifications, and constraint solving.

During NLP, a list of textual descriptions of pre, post and guard conditions in use cases is extracted. The
software engineer further manually reformulates these textual descriptions using OCL constraints based
on the domain model, iteratively refining the latter when required.

To enable the automatic identification of test scenarios and test inputs we combine Natural Language
Processing (NLP) with constraint solving. To extract behavioral information from use case specifications
by means of NLP we rely upon use case specifications expressed in a restricted form called RUCM. Since
RUCM was not originally designed for test generation, they introduced some extensions such as new
keywords and new restrictions on existing keywords. They employed OCL to refine guard, pre, and post
conditions automatically identified by NLP. They designed an algorithm that builds path conditions that
capture the constraints under which alternative flows are executed. The algorithm automatically
identifies test inputs by solving such path conditions with the aid of an OCL constraint solver.

The industrial case study shows that UMTG works well with use case specifications for an automotive
sensor system. The time required for test case generation enables the entire process to run over night.
Our experience indicates that the requirements modelling needed by UMTG is entirely feasible in an
industrial context.

This research paper proposed Use Case Modelling for System Tests
Generation (UMTG), an approach that automatically generates executable
system test cases from use case specifications and a domain model. To
extract behavioral information from use cases and enable test automation,
UMTG employs Natural Language Processing (NLP), a restricted form of use
case specifications, and constraint solving.
During NLP, a list of textual descriptions of pre, post and guard conditions in
use cases is extracted. The software engineer further manually reformulates
these textual descriptions using OCL constraints based on the domain model,
iteratively refining the latter when required.
To enable the automatic identification of test scenarios and test inputs we
combine Natural Language Processing (NLP) with constraint solving. To
extract behavioral information from use case specifications by means of NLP
we rely upon use case specifications expressed in a restricted form called
RUCM. Since RUCM was not originally designed for test generation, they
introduced some extensions such as new keywords and new restrictions on
existing keywords. The algorithm automatically identifies test inputs by solving
such path conditions with the aid of an OCL constraint solver.
The industrial case study shows that UMTG works well with use case
specifications for an automotive sensor system. The time required for test
case generation enables the entire process to run over night.