Tag: testing

Maintainability: multiple data-files are required for each Test Case.

Accessibility: Finding a perticular datasheet in a specific folder location is always pain.

Extensibility: scripts are not as extensible as in other frameworks.

Usablity: difficult to trace back error in unattended execution. Specially if recovery scenario is triggered during execution.

Keyword-driven tests look very similar to manual test cases.

Requires more extensive training in the test tool for people who will create tests.

The Detail Test Plan can be written in Spreadsheet format containing all input and verification data.

The tester need only learn the "Key Words" required, and the specific format to use within the Test Plan.

Less used framework because of it's limitations.

A Framework which is a combination of two or more frameworks.

Has essential components of this framework are Core Data Driven Engine, the Component Functions, and the Support Libraries.

Has App Map to bridges the automation framework with the application being tested.

Keyword Driven

Data Driven

Record & Play

All of the above.

True

False

Directory Structure

Function Library

Object Repository or App Map

Application Scenario Files

Driver Script

Sequence File

Modularity Driven Framework.

Model based Framework.

Context Based Framework.

All of the above.

Increasing Order

Decreasing Order

Order in which they were

None of these

Automatic notification alerts, Follow up alerts

Email alerts, Automatic notification alerts, Follow up alerts

Defect alerts, Email alerts, Automatic notification alerts, Follow up alerts

Final alerts, Email alerts, Automatic notification alerts, Follow up alerts

Convert Requirements to Tests & Generate a Test from Requirements

Convert Requirements to Tests & Convert a Test from Requirements

Convert Requirements to Tests & Generate a Requirement from Tests

Convert a Test from Requirements & Generate Requirements to Tests