Table of Contents
Test cases for Project Tracker web interface. PL/SQL API tests are included in the /project-tracker/sql/tests directory. These tests require utPL/SQL, which can be obtained from here. The tests here requires that the PL/SQL tests were successful.
Goal | Initializing Project Tracker |
Scope | Web interface, access control. /project-tracker/www/admin/initialize |
Case Triggers |
|
Primary Actors | |
Secondary Actors | |
Preconditions |
|
Success End Conditions |
|
Failure End Conditions |
|
Case Description | Test for the web interface for calling pt_project.new. Because there is only one root task per PT instance, this page should be accessible only once, and it should be the first page available to the user. |
Goal | Setting parameters for Project Tracker |
Scope | |
Case Triggers |
|
Primary Actors | |
Secondary Actors | |
Preconditions | |
Success End Conditions |
|
Failure End Conditions |
|
Case Description | Notification sender is the from: address in the notification email. This parameter is optional and defaults to registered users. It requires that the .info file is configured correctly. pt_util get's the current notification sender from the database. |
Goal | Ease of navigation by preserving URL query strings (page parameters) |
Scope | |
Case Triggers |
|
Primary Actors | |
Secondary Actors | |
Preconditions | |
Success End Conditions | Since these parameters are cached, you need to sign off to check these. Also check for #number at the end of the url string for the anchor tags. Possible actions that user can execute: The page parameters should be persistent through the above transactions |
Failure End Conditions |
|
Case Description |
|
Goal | Task modifications in PT is in sync with task description in Workflow. |
Scope | |
Case Triggers | User alters leaf task states editing task attributes after notification is complete (workflow case is started) |
Primary Actors | |
Secondary Actors | |
Preconditions | |
Success End Conditions |
|
Failure End Conditions |
|
Case Description | Ensuring that PT and WF are in sync. This is related to the interface between PT and WF. The same should be repeated by changing states in WF and confirming synchronization in PT. |
Goal | Ensure that PT and WF continues to stay in sync after task is started, especially after workflow task is canceled and and resumed. |
Scope | PT WF interface, .tcl page query |
Case Triggers |
|
Primary Actors | |
Secondary Actors | |
Preconditions | |
Success End Conditions |
|
Failure End Conditions |
|
Case Description | When a task gets canceled in wf, wf creates a new instance of the case that is labeled enabled, and leaves the canceled task behind. The correct wf_task must be queried and displayed to show useful information. |