Implementation Support System - ISS USER GUIDE Version 2.0
Page 4
Table of Contents Table of Contents...5 Revision History... 7 1.0 Introduction... 9 2.0 ISS Basics... 10 2.1 User Personal Computer Set-up Requirements... 10 2.2 Logging On/Off... 10 2.3 Navigation Tools... 11 2.4 New project set-up workflow... 12 2.5 Create Workspace Test Plan... 15 3.0 Project Management... 18 3.1 Site Maintenance... 18 3.2 User Maintenance... 18 3.3 Group Maintenance... 19 3.4 Status Overview Section... 20 3.4.1 Displaying Test Case Status for a Site... 20 3.4.2 Displaying the CSR Report for a Site... 21 3.5 Assign Test Cases... 22 3.6 Archive Data... 23 4.0 Test Planning... 25 4.1 The Master Test Plan... 25 4.1.1 Displaying MTP Test Cases... 25 4.1.2 Modifying MTP Test Cases... 26 4.1.3 Creating a new version of MTP test case... 27 4.1.4 Removing MTP Test Cases... 28 4.2 The Workspace Test Planning... 28 4.2.1 Site Test Plan Configuration... 28 4.2.2 Test Cases Creation Options and Data Fill... 30 4.2.3 Test Cases Addition and Removal... 30 4.2.4 Test Plan Approval... 31 Page 5
4.3 Checklists... 33 4.3.1 Generating the Checklists... 33 5.0 Test Implementation... 35 5.1 Project Overview Section... 35 5.2 Finding Assigned Tests... 37 5.3 Listing Test Cases... 38 5.4 Editing Test Cases... 39 5.5 Offline Test Cases Updates... 41 End of Document... 43 Page 6
Revision History Release Date Description Version 1.0 October 12,2005 Initial release Version 1.1 October 22,2005 Added changes from Nortel s review Version 2.0 March 19,2006 Added multi-project ISS capability Page 7
Page 8
1.0 Introduction The Implementation Support System (ISS) is a database infrastructure, which was built by Quasar Inc. It provides a managed service that facilitates the workflow of complex engineering projects. The ISS framework is aligned and customized to Nortel s Test and Verification (T&V) service delivery model. This document describes the usage of the ISS from the user perspective including project management, test planning and test implementation. The end-to-end T&V process workflow and main user functions are illustrated in Figure 1.1. Planning Implementation Site Data Collection Site Test Plan Development Site Preparation Test Case Execution T&V Acceptance Nortel User Work Functions: Generate Check List (Project Mgmt) Provision Data fill-optional Produce Site Specific Test Plan (Test Planner) Customer User Work Functions: Confirm readiness for testing (Project Mgmt) Coordinate & Perform Test activities, capture results, resolve problems (Tester) Deliver T&V Report (Project Mgmt) Provide Site specific Data; Provision Data fill Approve Site test plans Accept test Implementation Schedule Validate OSS results, e.g. Billing, Alarms, OMs Sign-off Test results Figure 1.0 Test and Verification process workflow In addition to introducing the basics of using the ISS through different categories of users, this document describes the ISS operations specific to various user work functions. These work functions include Project Management, Test Planning and Test Implementing. As depicted in Figure 1.0, these functions involve personnel from both Nortel and Customer organizations. Throughout this document both terms Test and Verification and Network Certification have the same meaning. Page 9
2.0 ISS Basics Implementation Support System ISS 2.1 User Personal Computer Set-up Requirements When using the ISS site, it is strongly recommended that you use Microsoft Internet Explorer as the web browser, version 6 or higher. This download is available at www.microsoft.com/ie/. If you have installed a pop-up blocking software, disable it while using the ISS site. Some projects may be enhanced with Macromedia Flash components. If you do not have the correct version of Flash, you will not see animation on the ISS login page. If this is the case, there will be a link at the bottom of the page to download the latest version of Flash. This download is also available at www.flashplayerpro.com. 2.2 Logging On/Off To log on to the ISS site, direct your web browser to www.issdata.com. You will be prompted to enter your user name and password, see Figure 2.2.1. Both the user name and password are case sensitive (usually all lowercase). Enter the information and click the Submit button. Figure 2.2.1 ISS log-in screens The system will attempt to validate the user name and password. If authentication is successful, you will be connected to the project section, which is specified by the project administrator when your account is created, Figure 2.2.0. Typically, projects have several work sections and system users will be assigned access rights within those areas. The access rights set up by the project administrator effect the way the project sections look, as well as the way the user interacts with the database (for example read-only vs. editing capabilities). Therefore two different users might have different initial views of the project. If there is an error validating your user name and/or password you will receive an error message and prompted to retry. Common causes of connection problems might be due to: User name and / or password incorrectly entered User name and / or password were entered in the wrong or mixed case (case sensitive). For example: entering JSmith is not the same as entering jsmith. Typically user names and passwords are all lower case. If you are unsure how your account was set up check with your project administrator. Your account may not have been created or your account might be inactive. Page 10
Figure 2.2.1 ISS log-in screens, cont d. If a connection problem persists, notify your Project Manager. Your user ID can only access the ISS from one computer at a time. If you try to log on from another computer, the next time you try to interact with the system from the first computer you will receive an error message and be logged off. 2.3 Navigation Tools The top section of ISS pages contains projects navigation tools, Figure 2.3.1: Figure 2.3.1 Access navigation tools Legend 1. Project Selection allows access to individual projects workspaces; The selected project expands into its Workspace Access Options entries; 2. The Workspace Access Options drop-down menu provides access to selected workspace areas, including Project Overview, Administration, Planning and Implementation areas. These areas expand into Project Options. 3. The Project Options window provides access to selected sections within the project workspace. The selected entries in the Project Options Window expand into Workspace Options; 4. The Workspace options window provides access to various project management and test planning functions. Page 11
In addition to the Project Options field, there is another type of data access selection commonly displayed on the left side of the screen throughout the ISS worksheets. The tool is associated with site test plans, commonly referred to as a Site Activity field. The content of the given Site Activity (such as Test Group) is identified by the location of its Call Server Complex (CSC) and the site location. Both location fields need to be selected from the drop-down menus as shown in figure 2.3.2. Figure 2.3.2 Navigations tools: site activity selection 2.4 New project set-up workflow The workflow of each ISS project consists of three phases: (a) project definition (b) planning (c) implementation As depicted in Figure 2.4.1, each phase has a series of steps. The project definition is the fundamental initiation of the ISS workspace impacting the scope and content of the subsequent phases. Some of the project definition steps can be re-entered for changes or additional set-ups, even if the project has already moved beyond project definition. The T&V Mater Test Plan (MTP) is a special type of workspace with its own function and controlling tools. The MTP workspace is described in further details in section 4.0. Page 12
Figure 2.4.1 Test and Verification ISS project workflow A new project starts with the initialization of its workspace. Only users with the rights of the ISS Administrator are allowed to perform this function. To initialize the new workspace the ISS Administrator selects the following the path: Project Selection (= TNV) => Workspace Access Options (= ISS Workspace Manager) => Project Options (=NEW), and clicks the Create New Workspace button in Workspace Options window; see Figure 2.4.2 below for details. Figure 2.4.2 Initialization of a new project s workspace All fields depicted in Figure 2.4.3 need to be filled out, including Customer name, Project name, Network Engineer (NE) Manager name, and the project map of the country in which the project is being performed. Click the Initialize tab in the bottom-right corner to store the information. Page 13
Figure 2.4.3 Enter new project s workspace identification Additional workspace information needs to be added in a new screen see figure 2.4.4 for details. For guided steps click on the Project Setup Map tab; this will open a new window with a diagram of the Test and Verification ISS project workflow. By selecting hyperlinks in the individual blocks, user will be guided to specific screens including: - Add users to workspace allowing registration of ISS project users; - Set Network Engineering (NE) manager adding the name of the NE manger responsible for T&V project planning; click on Edit General Information ; - Add CSC - editing properties for a new Call Server Complex providing CSC ID, name, address information, and marking the CSC location on the map; - Add Sites defining sites subtended to the Call Server; click on Add / Edit Sites link; - Create Workspace Test Plan assigning required test categories from the Master Test Plan (MTP); click on Add MTP tab and follow the following sections of solution, test level, and SW version fields. - Set TC Status to Active selecting applicable test cases within each test category; refer to Workspace Access Options = Workspace Test Plan to display selected test cases; Page 14
Figure 2.4.4 Enter additional workspace information 2.5 Create Workspace Test Plan The Workspace Test Plan (WTP) refers to the selection of test cases, which are applicable for the given project. These test cases are derived from the Master Test Plan (MTP) that serves a repository function of all test cases available to all T&V projects. The test case selection process for WTP leverages various attributes assigned to individual test cases. These attributes are organized as illustrated in the framework below: The WTP test cases are downloaded from the Master Test Plan by clicking the MTP tab on the project Workspace screen and selecting the test case attributes as illustrated in Figure 2.5.1. Page 15
Figure 2.5.1 Create Workspace Test Plan The WTP now has the entire set of test cases that can be further refined (activated or deactivated) according to customer requirements. In order to perform this, you need to select the desired category (e.g. Feature) from the Workspace Test Plan screen shown in Figure 2.5.2. Figure 2.5.2 Select WTP test cases Page 16
Figure 2.5.2a Select WTP test cases, cont d The Feature test cases are displayed as Inactive. In order to activate the test as an entire group or on a selective basis, you need click on Admin Tool tab and proceed with the additional steps using the Toggle and Select buttons. Please refer to Figure 2.5.3. Figure 2.5.3 Select WTP test cases, cont d Only Active test cases will be available for assigning them to site specific test plans refer to section 3.5 Assign Test Cases Page 17
3.0 Project Management Implementation Support System ISS 3.1 Site Maintenance Before site specific planning can begin, the work location must be added to the ISS if it is not already present. This addition can be made through the Site Maintenance section (accessible through the path: Project Selection -> Workspace Access Options. (See Section 2.3 Navigation and Information Tools for details). The Site Maintenance provides three tools to update: (i) Call server complex (CSC) information, (ii) sites information, and (iii) the CSC map. Each Site is referenced to a call server complex (CSC). When adding a site, you must first add its corresponding CSC if it is not already present. Please refer to figure 3.1.1 for details. Figure 3.1.1 Site maintenance workspace To add a CSC or a site, enter the information requested through the form that opens, and then save the location. The CSC does not need to be a work location, but each work location should be reference to the CSC to which it is associated. To edit data for an existing CSC or Site, click on its 4 or 6 digit ID to access the editor. 3.2 User Maintenance The User Maintenance section allows registering new users assigned to a project and controlling their access right levels according to their project role. The User Maintenance is accessible through the path: Project Selection -> Workspace Access Options. (See Section 2.3 Navigation and Information Tools and Figure 3.2.1 for details. To add a user, enter a proposed user ID in the edit box. If the ID is already in use, by this project or another within the system, you will be prompted to try a different ID. Page 18
Figure 3.2.1 User management workspace Once a user ID has been accepted, a form will open to enter the user s data. Enter user name, company name, email, initial password etc. It is recommended to enter an invalid password initially (< 6 characters), such as iss. This will force the user to change their password when they login onto the system for the first time. To allow users to access the system, they must have the account active right checked. Other rights determine options and sections that users will have access to; these rights are defined on a project to project basis. If a user has not accessed the system within 90 days, their account will be marked inactive. A project administrator will need to reactivate the user s account before they can regain access. To switch back on, the project administrator must access the inactive user s page, select the user ID, and then check the account Active option. 3.3 Group Maintenance The Group Maintenance section is accessible through the path: Project Selection -> Workspace Access Options. (See Section 2.3 Navigation and Information Tools and Figure 3.3.1 for details. To add a group, select the Add a new Group option from the drop down menu, and rename the group. Then click the Add/Remove Users button to assign/remove users from the group. The group will then be able to access parts of the site that reference groups as a part of the workflow process (i.e. test case work assignments). Page 19
Figure 3.3.1 Group maintenance workspace 3.4 Status Overview Section The Status Overview section is accessible through the path: Project Selection -> Workspace Access Options. (See Section 2.3 Navigation and Information Tools and Figure 3.4.1 for details This part of the project management workspace provides two types of status reports: Test Case Status and CSR Report. (i) (ii) Test Case Status is a progress report of the test cases, on a per group basis for each CSC test location. Status of problem reports, which can also be referred to as Clarify Service Requests (CSR), can be accessed by clicking on the Status Overview: CSR Report link on the top right side of the menu. The report, which is structured in an action register format, shows details of test cases which require a follow-up activity to resolve testing gating issues. See Figure 3.4.2 for a sample of CSR report. 3.4.1 Displaying Test Case Status for a Site The Test Case Page displays a list of the different categories of test cases. Each category tells the user how many test cases have been planned for that category; what the status of those cases is (Planned, No status, Assigned, Under Review, Executed, Passed, Failed or Not Applicable); the percentages of tests that have fails; and the number of tests which have been completed including their overall Pass rate. The following are definitions of terms used within the test status: Planned: all originally approved test cases; Page 20
No Status: approved test cases waiting to be assigned by the Project Manager Assigned: test cases ready for execution; Executed: test cases implemented with recorded test results available; Under Review: test cases, which results are being examined; pending further decisions; Passed: test case results agreed to as expected and accepted; Failed: test cases which did not meet expected results; require reexecution; Not Applicable: initially planned, however, subsequently agreed to be excluded from the scope of testing. See Figure 3.4.1 for an example of the test case status report depicting progress of test activities at Woodstock test site, which is part of the Atlanta CSC. Figure 3.4.1 Test case status report example If you click on one of the numbers in the status report matrix it will take you to a list of all of the test cases represented by that number. 3.4.2 Displaying the CSR Report for a Site The CSR Report option will take the user to a list of all of the CSR s for the current site. Clicking the Status Overview: CSR Report link on the top left menu bar will bring up a window for changing the current site. Page 21
Figure 3.4.2 Customer service report (CSR) example The CSR Report shows a basic description about the CSR s, the user who entered the CSR, and some other basic information. To find out more about a CSR the user will have to visit Nortel s site. By clicking on the link in the leftmost column you will be directed to Nortel s Clarify system login screen. 3.5 Assign Test Cases The test cases that are marked approved are assigned to either an individual name and/or test team name, which indicates who will be responsible for the implementation of the test cases. Refer to section 3.3 Group Maintenance, for an explanation of how to create names for test teams. The Assign Test Cases function is accessible through the path: Project Selection -> Workspace Access Options. (See Section 2.3 Navigation and Information Tools and Figure 3.5.1 for an illustration of how to assign test cases). Page 22
Figure 3.5.1 Assigning test cases 3.6 Archive Data The Archive Data Section is accessible through the path: C2P Project -> Network Certification -> Project Overview: Archived Data Sets (see Section 2.3 Navigation and Information Tools, for details). The Archived Test Cases option will take the user to a national map that shows which sites have any archived test cases. By archiving test cases, the user can do his/her planning in stages. For example, the user can conduct one group of test cases, and then when completed, could archive that set of test cases and start fresh with the next group. Figure 3.6.1 Archive data workspace Page 23
The color-coding shows the user which sites have test cases archived. Blue sites do not have any archives, whereas the green sites do. If the user clicks on one of the sites he/she will be taken to a page listing the archives available for that site. To change the site s current test cases data into an Archive state, go to the Control Panel and click on Request Site Archive. This will open up a dialog box requesting the site Location ID to be archived. Page 24
4.0 Test Planning Test planning can be performed at two levels: Master Test Plan (MTP) and projectspecific Workspace Test Plan (WTP). MTP planning involves creating and maintaining test cases shared among all projects (and their ISS workspaces), while project-specific WTP planning is associated with selecting individual test cases and adding a site-specific data information to the test cases. 4.1 The Master Test Plan The Master Test Plan (MTP) Section is accessible through the path: Project Selection - > Workspace Access Options. (See Section 2.3 Navigation and Information Tools and Figure 4.1.1 for an illustration how to assess MTP). The MTP is a repository of test cases supporting all T&V projects (e.g. Verizon, Sprint Bell Canada). The changes made to the MTP cases may impact the content of test cases within project WTPs (e.g. Sprint) but not the other way around. The ISS master test plan editor provides the functionality of defining new test cases and tracking current and historical test cases. Figure 4.1.1 Master Test Plan workspace Figure 4.1.1 shows the starting point after the user selects appropriate filters and grouping options from the control panel. Tests are primarily categorized by a layer, solutions and category as described in detail in Section 2.4.1 Create Workspace Test Plan. Each test category contains a collection of tests with similar characteristics. Tests are also categorized by a solution; however tests can belong to more then one solution. 4.1.1 Displaying MTP Test Cases Select a specific test category to display a group of tests. At any time, you can narrow the number of tests or groups that are available for selection by choosing Page 25
the appropriate filters. If a higher level filter is not selected, then all tests in a given category will be displayed. The test case listing (Figure 4.1.1.1) shows shade coded test cases and their status for a selected test category. The gray color indicates an active status (e.g. test case being used in at least one the workspaces. The white color indicates a test that has not yet been selected. Figure 4.1.1.1 MTP Test Case Listing Columns in this illustration list the test ID, test version, test description and the number of active test instances in the project workspace. You can click on the test ID to display details of an additional test and make modification to the test. 4.1.2 Modifying MTP Test Cases Tests can be modified to the master test plan by clicking on ADD NEW TEST link in the MTP Controls Panel on the left side of the screen. The following three options will be offered to the user to decide how to change a test case: - NEW TEST CASE - No existing prototype in test plan - CLONED TEST CASE - Test created using the template of an existing test - NEW VERSION OF TEST CASE - Test replacing or updating an existing test By selecting one of the choices above, the user will enter either a new test category, or they will select the test case that needs to be modified. Either a new test case ID number will be assigned for this action or a test ID suffix will be added. Page 26
4.1.3 Creating a new version of MTP test case Implementation Support System ISS In general, new versions of a test are meant to retain the basic characteristics of the original test in regards to the testing objective. If a new test has a similar structure to the original, but has a different purpose behind its objective, consider selecting the "CLONED TEST CASE". This option provides the ability to create and adjust a distinct test, rather then a new version. When a new version of an existing test is created, the old version can either become obsolete, inactive or remain active in the test plan. The "OBSOLETE" designation should be used when a new test supersedes the existing test and there is no circumstance where the original should be used in the creation of test plans. An "INACTIVE" status will keep the test in the planning area of the test plan, but it will not be available for selection in the implementation phase. Allowing a test to remain "ACTIVE" indicates that both the new and original versions of the test can be used in the implementation phases, under the same or different circumstances. Regardless of the chosen selection, tests, which are currently part of site, test plans, in the planning or implementation phases will not be effected. Figure 4.1.3.1 Creating a new version of the MTP test case Page 27
4.1.4 Removing MTP Test Cases Test cases are never deleted from the database. Depending on the circumstance, they are either overwritten, replaced with a new version, or disabled from the test plan creation menu. To disable a test case from the MTP menu, the test case must be selected from the test case list (accessible through the path: Project Selection -> Workspace Access Options = Master Test Plan, see Section 2.3 Navigation and Information Tools). Once the test case is opened, the ACTIVE vs. INACTIVE status change option can be toggled by a button that is found under the test ID field. 4.2 The Workspace Test Planning Once the Workspace Test Plan (WTP) is created for a project (see section 2.4.1 Creating the Workspace Test Plan), it can be further customized to satisfy the need of its implementation. This WTP becomes a centralized selection of test cases for the test sites defined within the scope of the workspace. This part of the T&V process consists of the following steps: - Site Test Plan Configuration - Adding and Removing Site Test Cases - Test Case Data Fill - Test Plan Approval - Project Scheduling - Check List Creation 4.2.1 Site Test Plan Configuration The site specific set-up supports the creation and the management of the site s test cases. See Figure 4.2.1.1. The box on the left shows test categories and quantities of test cases in each category. The box on the right provides controls for managing operations to the site specific test plans. Page 28
Figure 4.2.1.1 Managing site-specific test plans When a particular test category is selected (click on a blue icon) the box on the right will display options for managing test cases within this test category. The controls include adding, removing, data filling, approving, downloading, uploading, and assigning test cases. See Figure 4.2.1.2 Figure 4.2.1.2 Managing test cases Page 29
4.2.2 Test Cases Creation Options and Data Fill Test cases can be created by adding them individually through the Test Group option (of the Workspace Test Plan), or by copying them from another location. Another option is to add them from an archived location. See Figure 4.2.1.1. Figure 4.2.2.1 Data fill of test cases Test cases data fill (see Figure 4.2.2.1) provides tools to add or alter specific test case parameters such as CTP (certification test point), originating DN, termination DN, and Trunk CLLI. The data fill can be added to either individual test cases or to a pre-selected range of test cases. The Search and Replace tool allows you to find and modify the values of the existing test case(s) data fill. After clicking on Search and Replace button just use the opened dialog box fields for your editing needs. The Mark-up Mode button is used to highlight selected test cases for the purpose of getting attention. As a result, these test cases will be displayed on a yellow background. If not needed, the yellow mark-up can be removed. 4.2.3 Test Cases Addition and Removal Once created, the groups of test cases can be further modified through additions or removals of individual test cases. Please note that the test cases can be removed when they have a proposed status. New test cases can be added at any time. To perform a desired modification, select a particular test group, and click on the proper operation displayed in the Options box. Follow on-line instructions for the remaining steps, as illustrated in Figure 4.2.3.1 and Figure 4.2.3.2. Page 30
Figure 4.2.3.1 Modifying test groups: adding new test cases Figure 4.2.3.2 Modifying test groups: delete/remove test cases 4.2.4 Test Plan Approval Once the test groups are created and test cases are data filled, the site specific test plan is ready for approval. The Approved status confirms test case readiness for the implementation phase see Section 3.5 Assign Test Cases. Page 31
To perform a test case approval, select a particular test group, and click on the proper operation displayed in the Options box, i.e. if you approve the entire group click on Approve All Proposed Group-name Tests, or to approve an individual test case within the group click on Approve/Edit Individual Test Cases from the Current Set of Group-name Tests. Follow on-line instructions for the remaining steps, as illustrated in Figure 4.2.4.1 and Figure 4.2.4.2. Figure 4.2.4.1 Approving test groups Figure 4.2.4.2 Editing and approving test cases Page 32
4.3 Checklists Implementation Support System ISS The purpose of checklists is to record and manage pre-requisite data required for testing. The checklist data is used to generate site-specific test cases and facilitate the implementation of test cases. 4.3.1 Generating the Checklists To generate a new checklist for the given CSC, select the desired CSC site from the Project Overview map CSC Checklist option. After opening the CSC checklist workspace, click the Admin Mode button (upper right corner) and decide which Checklist Creation Option you wish to use. You can select either Create or Insert Template as illustrated on Figure 4.3.1.1. Figure 4.3.1.1 Generating checklist from Create and Insert To create a checklist, you can either create a new template (Create Template), or you can consider using the existing one (Insert Template). Before you start creating a checklist template in the ISS, you should design an off-line sketch of the checklist layout. The layout is a matrix of rows and columns providing a list of deliverable items and associated fields. For example, details of delivery methods, schedules, contact information and other data are found within the matrix. The matrix can capture delivered information in a form of text data, or as attached files. Each item on the list can have a variable number of fields, i.e. columns, dependent on the type of required information. Once you have completed the design of the checklist layout you can create the ISS on-line template, as illustrated in Fig 4.3.1.2, by using add new form in the formatting options. Page 33
Figure 4.3.1.2 Creating checklist form To re-use the existing checklist format to create a new template, select the existing site s checklist from the Project Overview Site Checklist, click the Admin button, and click Create Template. As instructed, enter a template name, under which the template s image will be saved. Next, select the targeted CSC (this CSC must not have an existing template in order to use the insert function), click on Insert Template, select the template s name and click on Submit. A copy of the template becomes the site s checklist. Other actions include Delete the checklist, and Archive the checklist. You can also modify the checklist by selecting the rows or adding new items (see Figure 4.3.1.3). Figure 4.3.1.3 Modifying checklist format Page 34
5.0 Test Implementation 5.1 Project Overview Section The national project map in the project overview section shows a graphical representation of all projects locations. It serves as a way of checking on the overall progress of the sites nationwide, and as a way of navigating ISS to get to the information the user needs. Figure 5.1.1 National project map If the user clicks on one of the sites on the map, they will be taken to the Status Overview page for that site. The map s legend in the bottom left corner of the map, will explain what all of the color-coding on the site points mean. A blue dot is a site that has been put into the system, but has not yet been given test cases. Red dots are sites that are in their planning stages. This is when they have some test cases, but not all of them have been approved yet. Yellow sites have had all of their tests approved, but not all of them are finished yet. Moreover, green sites have 100% of their test cases finished. Other information displayed on the map is listed in the options menu in the top right corner. For example, if a user has been assigned any deliverables on a CSC Checklist then - Assigned Deliverables will appear after the CSC Checklist option. Selecting this option displays the CSC datasets graphically on the national project map (see Figure 5.1.2). The CSC Checklist page resembles the National Project Map. It uses the map of the United States with color-coded sites. The color-coding on this map pertains to the site s CSC Checklists instead of their test cases. Page 35
Figure 5.1.2 National CSC Checklist Map The colors on the sites indicate whether a site has a CSC Checklist available. Blue means there is no checklist, yellow means that there is a checklist, and green means that there is a checklist and the current user has a deliverable assigned to it. Clicking on one of the sites will take the user to that site s CSC Checklist page, see example Figure 5.1.3. Figure 5.1.3 CSC Checklist display If the current user has a deliverable assigned, they will be able to edit the information on the row they were assigned to by clicking on one of the blue triangles beside the information. Page 36
5.2 Finding Assigned Tests Implementation Support System ISS To find test cases that have been assigned to your user ID using the systems work assignment functionality, use the navigation tools to switch to the Test Case Work Assignments screen accessible through the path: Project Selection -> Workspace Access Options = Project Overview -> Project Options = Test Case Work Assignments, see Section 2.3 Navigation and Information Tools) Test assignments will be listed for the selected Call Server Complex (CSC) and site. If there are no assignments for a particular site, a message like the one shown in Figure 5.2.1 will be displayed, otherwise, with test cases assigned to a user, the screen would look like Figure 5.2.2. Figure 5.2.1 Test case assignment: an empty list Figure 5.2.2 Assignments of test cases Page 37
If you are assigned test cases in the site(s) that you have selected then they will be displayed below the data set box. The tests are listed per Test Set. Test sets are a grouping of test cases by Site, and then by test category. The display of assigned test cases also breaks the test cases down by current status. In this section, the word Assigned has two meanings. First, it means that the responsibility for executing, passing or failing a test has been assigned to your user ID. The second meaning refers to the status category called Assigned. Information about testing procedures will be discussed in more detail in section 5.3, but this example uses the previous point in considering test cases in the Billing test category. Nortel executes the Billing tests onsite. The determination of whether the test passes or fails is then made by the Customer once the billing records are checked. In this phase, the Nortel employee who is assigned to the test will be working with test cases within the Assigned status category. Customer personnel, on the other hand, will only work on test cases in the Executed status category. It is for this reason all of the test cases that are visible on this page are test cases that are assigned to you, regardless of their current status. 5.3 Listing Test Cases From the test assignments page, you can click on the title of a test set link to bring up a listing of all the test cases in that category, regardless of their current status. Otherwise, you can click on one of the square test status icons to list a subset of test cases based on their current status. The default listing page will show detailed information about the selected test cases. From this page you can click on any test case ID to access a specific test, see Figure 5.3.1. Figure 5.3.1 Getting access to assigned test cases Page 38
The Figure above, displays 2 fields. The first field contains controls for selecting the format of the way you view the format of the test case lists. The test case title consists of the site code, the status of the listed tests, the test category and your user ID. Below the title is a drop down menu that you can use to change the format in which the data is displayed. The Detailed view is the default for every list. Other options include a Brief view and a Printer Friendly view. The second field, contains the test cases themselves. To print this list select the Printer Friendly view, and go to File -> Print in your web browser. If you are printing on letter size paper, you should switch to the Layout tab and select Landscape orientation. 5.4 Editing Test Cases From the test case listing, you can select any test ID to go to the detailed view of an individual test case. Once inside a test case, the list from which you selected that test case will be remembered so that you can then move back and forth between other test cases in the same group by clicking the left and right arrow tabs on the top right corner of the test case box, Figure 5.4.1. Figure 5.4.1 Test case data update form The test case window will contain the most detailed information available about a specific test case. The fields with a gray background contains read-only information containing descriptions and expected results, as well as additional comments about how to execute the test. The fields with a white background and blue text are editable fields. The information in these fields was filled out during the planning phase for the site. There are times when the availability of resources and other concerns within the fields might require change. The data in these fields should accurately reflect the equipment and test lines that were used during the test execution. To modify a field, click on the blue text to open up an edit box, make the changes and click Update. Page 39
The next three fields contain places for notes, test files and references for the Clarify Service Request (CSR) system. The number and types of notes which are entered should be explained in the comments section; this includes test execution guidelines and other official test case materials. In addition, notes should be entered to explain any abnormal results or special circumstances that arose during the course of execution for that particular test case. The notes will serve as a primary record of the details of a test case history and should be as complete as possible. To make a note, fill in the text in the edit box and click the Add Note button. Your user ID will automatically become part of the note information. You can modify or delete notes that you have entered by clicking on the noted text. To delete a note, click the delete button then confirm your selection. Test result files are considered both log files and generated screen shots that have been taken during test execution. These files provide a record, and they also justify why a test passed or failed. To upload a file, click the Browse button. This will bring up a Choose file dialog box. Locate the file on your computer and click Open. This will subsequently fill in the correct file name in the appropriate field, see Figure 5.4.2. To upload the file, click the Upload button. *IMPORTANT: The file does not become part of the test history until you click the Upload button. Uploaded files can be viewed by clicking on the file name. You can delete files that have been uploaded by clicking the delete link next to the file, then by confirming your selection. If there is a problem with test case execution that cannot be immediately resolved or if a test case fails, an entry should be made into the Clarify system and cross-referenced in the ISS system. To add a Clarify Service Request, click the Add CSR button on the test case. To register a service request, enter the CSR number, any comments about this CSR, and a classification of whether or not the problem is service effecting. Figure 5.4.2 Updating test case form Page 40
The final two fields in the test case box are the time stamp and the current status of the test case. The timestamp should accurately reflect the date and time that the test case was executed. Some test cases will be validated for execution success by comparing the timestamp with the switch time when an event was logged. For this reason, the time should be adjusted to local time of the test execution site. Only the last timestamp is saved, so you can always start by clicking the Now button to ensure that you have the correct date format in the field. Then you can make any adjustments necessary to the time and/or date. Use the Save button to save both the time and the current status. If there is a mismatch between the switch local time and the ISS timestamp for your site, you have the option to adjust the ISS time by clicking on the Save and Set time Now button for this Site. Clicking this button will use the current value of the time field to update the site so that, and in the future, whenever you or anyone else clicks the Now button the time will be recorded accurately. You can also clear all values from the time field by clicking the Clear button. Finally, the status field shows the current status of the test case. Select the status from the drop down menu and click Save to update this field. When you change the status of a test a note will automatically be generated for the test case confirming the change, as illustrated in Figure 5.4.3. Figure 5.4.3 Changing test case status As described earlier, there are several types of test cases that will go through an Executed status before they are declared Passed or Failed. For example, the test cases in the Billing and Alarm groups fall into this category. 5.5 Offline Test Cases Updates If the user does not have Internet access to update test case forms, an off-line update can be implemented by creating a.csv file image of the selected group of test cases. To create and download a.csv file to a user s computer, the user needs to select the Page 41
particular group of test cases as shown in Figure 5.5.1, and initiate the download of the csv file by clicking the download csv file bar. Figure 5.5.4 Downloading test case csv file After completing updates to the csv file on the user s computer, the file should then be uploaded to ISS. The updated fields will propagate throughout the date base and will overwrite the previous values. Therefore, special precautions need to taken to ensure that the assigned tester is the only person who does the data updates during the offline mode of operation. Figure 5.4.5 illustrates the uploading of a test case csv file to ISS. Figure 5.5.5 Uploading test case csv file Page 42
End of Document Page 43