DECA-project - Software Test Cases

DECA-project - Software Test Cases
© 2002 DevTeamware-group

Version 1.2 : 21. 3. 2002 Tomi Kärkkäinen

Version history:

V1.0 - 9.2.2002 - V1.0 is included in Software Testing Report #1. Contains scenarios 4.1 and 4.2.

V1.1 - 12.3.2002 - Added scenarios 4.3, 4.4, 4.5 and 4.6. Made requirement 4 to be a separate test step.

V1.2 - 21.3.2002 - Added requirement 8 plus, and lots from Functional Specification v1.9: Removing Document, Copying Document, Create/remove/move chapter, Browsing Comments, etc.

1. Introduction

This document lists the functionality (black box) test cases for the DECA project. The steps (functions) of the cases are mostly requirements, since that is the way the scenarios are in requirements specifications.

2. Test Environment

The test environment (operating system, Tomcat, J2EE, db4o) is described in the DECA Technical Specification. The web browser used in the testing is MSIE 5.5 service pack 2, under Windows 2000 Professional with Service Pack 1. Most of the testing is done with a display resolution of 1024x768.

3. The Tests

3.1 Test of scenario 4.1 (Documents)

Function: Requirements 1, 2 and 3

Test description: One can open a document by entering a URL to the browser. There should be authentication of users.

Acceptance criteria: After entering the URL, DECA opens the document in browser after authenticating the user.

Result:

Observations:

Function: Login Function

Test description: The username and password grant access and open the Welcome to DECA view.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 4

Test description: One can read a documents with DECA.

Acceptance criteria: Must be usable at a 800x600 resolution too.

Result:

Observations:

Function: 3.5.2.1. Browsing Related Documents

Test description: The documents belonging to the same group are presented to the user in a menu like fashion so that the user can easily change between the documents.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 5

Test description: One can view two documents side by side.

Acceptance criteria: Must have two frames showing the documents, or be able to position two separate browser windows for dual reading.

Result:

Observations:

Function: Requirements 6 and 7

Test description: Start a new document. Select a template as the basis of the document.

Acceptance criteria: A new document cannot be started from scratch, must start from a template.

Result:

Observations:

Function: Requirement 8

Test description: The system must have a text editor.

Acceptance criteria: Must be able to edit existing documents. Must be usable at a 800x600 resolution too.

Result:

Observations:

Function: Requirement 8 plus

Test description: Document editing - additional features. Can insert line breaks (<BR> tags). Can insert inline images (<IMG> tags). Can insert hyperlinks (<A HREF="">).

Acceptance criteria: -

Result:

Observations:

Function: 3.3.5.1. Creating Chapter, 3.3.5.2. Removing Chapter

Test description: Document editing - Can insert a new chapter at desired point in the document. Can remove a chapter.

Acceptance criteria: Removal must remove all sub-chapters of removed chapter.

Result:

Observations:

Function:                    3.3.5.3. Moving Chapter (Cut and Past)

Test description: Document editing - Can move a chapter inside a document.

Acceptance criteria: Moving takes all the sub-chapter of moved chapter with it.

Result:

Observations:

Function: Requirement 9

Test description: Attaching a document to a document.

Acceptance criteria: -

Result:

Observations: Too vague wording in the scenario and the requirement.

Function: Requirements 10 and 11

Test description: 10: Granting read document, edit document, comment on document and comment analysis rights to users. 11: Adding metadata such as keywords to help users find the document.

Acceptance criteria: -

Result:

Observations:

Function: 3.3.4. Copying Document and 3.5.2.2. Selecting Document Group (moving to other group)

Test description: An existing document can be copied or moved to another document group and name.

Acceptance criteria: The system will verify that the group-name combinations will remain unambiguous.

Result:

Observations:

Function: 3.3.2. Removing Document

Test description:               An existing document can be removed from the system.

Acceptance criteria: Removing a document requires special privileges.

Result:

Observations:

Function: Logout Function

Test description: Clicking on the Log Out link should log the user out of the system.

Acceptance criteria: -

Result:

Observations:

3.2 Test of scenario 4.2 (Find documents, Add comment)

Function: Requirement 12

Test description: The system can list what documents it contains.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 13

Test description: Find documents by document type.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 14

Test description: The system must show the relationships between documents.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 15

Test description: User must be able to add a comment to a chapter.

Acceptance criteria: Must be usable at a 800x600 resolution too.

Result:

Observations:

Function: Requirement 16

Test description: Many users can edit the same document.

Acceptance criteria: -

Result:

Observations:

3.3 Test of scenario 4.3 (Analyzing comments)

Function: Requirement 17

Test description: User must see the amount of comments in a document, and/or the timestamp of the latest comment.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 18

Test description: User must be able to read the comments.

Acceptance criteria: Must be usable at a 800x600 resolution too.

Result:

Observations:

Function: 3.4.2. Browsing Comments (also requirement 18)

Test description: Should have five different views into the comments, basic, advanced, basic printable, advanced printable and Filtered Comments View.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 19 (also 3.5.1.2. Selecting Comment Category)

Test description: A user with analysis rights can sort the comments into analysis groups.

Acceptance criteria: -

Result:

Observations: Error 2. "If someone is setting the comment category, the user is notified." Seems impossible to implement with current code.

Function: Requirement 20 (also 3.4.2.5. Filtered Comments View)

Test description: Users can view the comments sorted by analysis group. Shows only the comments belonging to the specified group(s).

Acceptance criteria: -

Result:

Observations:

Function: 3.5.1.3. Selecting Comment State and 3.5.1.4. Removing Comment

Test description: The user can select between unprocessed and processed states. Initially all comments are set to unprocessed state. The inactive state is set by the remove comment function.

Acceptance criteria: -

Result:

Observations:

3.4 Test of scenario 4.4 (Templates and comments)

Function: Requirement 21 (and 3.6.1. Creating Template)

Test description: User can create a new template within DECA. Must report an error if enter an existing template name to the new template.

Acceptance criteria: -

Result:

Observations:

Function: 3.6.5. Editing Template

Test description: Must be able to edit an existing template in the system if have the necessary user rights.

Acceptance criteria: -

Result:

Observations:

Function: 3.6.2. Removing Template

Test description: Must be able to remove a template from the system if have the necessary user rights.

Acceptance criteria: -

Result:

Observations:

Function: 3.6.4. Copying Template

Test description: Must be able to copy a template in the system if have the necessary user rights.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 22 (and 3.5.3. Changing Parent Template)

Test description: A document's "parent" template can be changed to point to another template.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 23

Test description: Comments have states such as "not yet done", "done" and "inactive". The analyzer role must be able to change a comment's state. Default state must be "not yet done".

Acceptance criteria: -

Result:

Observations:

Function: Requirement 24

Test description: User can add comments to existing comments. (Probably unlimited nesting depth.)

Acceptance criteria: -

Result:

Observations:

3.5 Test of scenario 4.5 (Version management)

Function: Requirement 25 (and 3.7.1.1. Version Naming) (and 3.7.2. Advanced Version Management)

Test description: A document can be labeled as "official" or be given a name. Then the document gets a version number and/or a name.

Acceptance criteria: All of a document's comments are set to the "inactive" state when set as a official version.

Result:

Observations:

Function: Requirement 26 (and 3.7.1. Basic Version Management)

Test description: DECA can display old versions of a document.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 27

Test description: A document can be printed out, with or without comments.

Acceptance criteria: -

Result:

Observations:

3.6 Test of scenario 4.6 (Report of same-template chapters)

Function: Requirement 28

Test description: User can select chapters from the template for the report.

Acceptance criteria: -

Result:

Observations:

Function: Requirement 29 (and 3.6.7. Generating Report)

Test description: DECA can generate a report that shows all the selected-in-template chapters from the documents that are based on the template in question.

Acceptance criteria: -

Result:

Observations:

Function: 3.6.8. Verify Template Compliance

Test description: This function is used to verify that the document fulfils the requirements of the template it is based upon.

Acceptance criteria: Not going to implement this.

Result: No result.

Observations:

3.7 Miscellaneous tests

Function: 3.8.1. Show Statistics

Test description: Shows information about the use of the system on a general level such as number of comments submitted per week, number of document retrievals, etc.

Acceptance criteria: -

Result:

Observations:

Function: 3.9. User Dependent Views

Test description: A) If a comment is marked as read, the system will not display it to the user, if all the sub-comments are also marked as read. B) If a chapter is marked as read and all its sub-chapters are marked read as well, the software will show it normally. Otherwise it will somehow emphasize the chapter.

Acceptance criteria: -

Result:

Observations:

4 Summary