SAMPLE FRS FOR TEST ENGINEERS

Quality management system

Test Engineer Assessment
Test software requirements specification

Version 1.0

Author:

1.1. Guidelines for Candidates

Please read the subsequent sections very carefully. The subsequent sections contains the specifications of an application, which need to be tested.

·         You can use any test case template of your choice. It could be in MS Word or in MS Excel.

·         Focus on testing the functionalities, features and UI of the application, whose details are given below.

·         You have 15 minutes to read the instructions (this document) and another 180 minutes to complete the test case documentation.

·         You will be evaluated on :

o    Exhaustiveness of the test cases, which covers all the application functionalities, features, UI etc.

o    Readability & how structured your test cases are.

o    English language, grammar.

o    Ease of understanding and ability to execute.

o    Relevance.

1.2. UC-4: Manage users (Create/update/delete users)

Scope	N/A
Primary actor	Super administrator
Stakeholders and goals	Super administrator: wants to CRUD (Create/Update/Delete) all kind of users
Preconditions	Administrator is logged in
Post-conditions	User is created / updated / deleted

…..

1.2.1.      Extension (UC-4.6): retrieve users

1.    Administrator requests to retrieve users

2.    System prompts administrator with list of users. See UI considerations

…..

1.2.2.      UI considerations and data dictionary: list of users

The users are displayed splitted on pages. The following columns are present in the list

Column	UI considerations	Sorting
Select	A checkbox which allows to select user for a batch operation	No
First name + Last name	Static text	Yes NOTE: sorting will be done first by last name and then by the first name (in spite of first name is displayed first)
Username	Link to user details	Yes
Email	Static text (non-mandatory field)	Yes
Status	Icon	Yes

1.2.2.1.                        Filter form

The user’s list filter is located at the top of the list and consists of the following fields, which can be used together, treated according to “AND” rule

Form field	UI considerations	Obligatory
Text search	Textbox, 255 characters Searching will be done in the following fields: -       First name -       Last name -       Username	No
Status	Drop down with values -       All -       Pending approval -       Active -       Inactive	No

 

1.3. Design constraints

1.3.1.      Support languages

Application will be implemented with only one user interface language – German.