Glossary|Qulix QA

Main Knowledge base Glossary

Our Clients

Clients about us

I was impressed with your attitude, guys. Feedback to my requests was received immediately and it was really easy for me to supervise the project from start to finalization. It is the first time I have had successful experience of speaking a common language with an offshore team.

William Greening

CTO

Clients about us

With the cooperation of Qulix QA specialists we have effectively deployed an end-to-end solution IBM Rational in order to run automated functional and load testing for a large-scale industrial enterprise in Russia. SM-Consult together with Qulix initiated the development and implementation of methodology and technology for automated functional testing and provided training programs for in-house staff. Thank you for much-needed expert help!

Alexander Novitchkov

Clients about us

We appreciate Qulix team’s immediate help with our enquiries and high-quality testing. Working with professionals is always pleasant.

Natalia Zhiltsova

Software Quality Assurance Department Manager

Test plan – a document describing the scope, approach, resources, and schedule of intended testing activities.

Test scenario (test suite) – a document set of test cases classified by testing types, functions and other parameters. A test scenario may be presented as an MS Office (Excel, Word) document or take the format of an automated software test management system file (HP Test Director, IBM Rational Test Manager, etc.).

Test case – a document containing a detailed description of a test for one or more system features with indicated specific data needed to start the test and keep it running as well as predicting test results.

Data-driven testing – data-driven method is used in software test automation and represents the type of testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet.

Keyword-driven testing – this type of testing is also known as table-driven or action-word testing; it represents a common technique in automated functional testing and takes two stages: framework design and implementation.