Test Cases

1). Designer:

  Test Case Expected Results Actual Result Date Tested
1 Opening the Designer Tool Click on the Designer tool and it must open without any error    
2 Login Login to the designer with correct user name and password    
3 Data source Name  Universe Connection should be made appropriately with respect to the development/test/Production environment.    
4 Connection Parameters Create connection based on the Database and mention the appropriate credentials. Environment should be known and the connection must be set respectively.    
5 Data Source Description Give the Brief Description about that particular Data source in properties –> Description    
6 Connection Testing Once the login credentials are provided, when the test connection button is clicked, ‘server is responding’  message should be obtained    
7 Classes and Objects Required tables and columns must be present in the database for BO to access    
8 Name of Objects Objects’ name should match with Requirements(needs to be verified by users/client during Requirement Analysis or Design as this name is visible to users)    
9 Object  Types Appropriate dimension, detail and measure objects available    
10 Object  data type Provide appropriate type of data being taken: Numeric/Char/Date/Long Text    
11 Where Clause Provide where clause if necessary and check whether it is appropriate as per the requirement    
12 Classes  and Subclasses  Structure Design of class and sub-class has to be in sync with the design doc of the Universe, based on the structure design.    
13 Name of  class /Sub-class Class name should match with Requirements(needs to get verified from users/client during Requirement Analysis or Design as this name is visible to users)    
14 Description Give a brief description of the Class/Sub-Class in Description    
15 Joins Joins should be appropriate based on the requirement and database structure    
16 Loops If loops has been resolved by alias or context.    
17 Contexts Proper definition of context with names and description.    
18 Alias appropriate name of alias and  description    
19 Universe structure Universe structure should be always up to date to universe. Check for the same    
20 Cardinality Cardinality should be defined.    
21 Integrity check do a quick integrity check for the universe and solve any errors before export to repository    
22 Check for loops in universe No loops    
23 Check and make sure that the Universe description is properly incorporated in the universe. Should be defined as per the requirement.     
24 Check for the linked/derived universe and record the name if it is present Should be defined as per the requirement.     
25 Check for the linked/derived universe and make sure the .LOV files are associated with derived objects which have been taken care. should be defined as per the  requirement    
26 Check for prompt and filter conditions Should be defined as per the requirement.    
27 Check for any error in definition of Hierarchies. should be defined as per the  requirement.    
28 Saving the universe Click on File → Save, the universe must be saved with .unv extension    
29 Exporting the universe Click on File → Export, the universe must exported to required domain and ‘Universe Exported Successfully’ message must be obtained    
30 Exit the designer Click on File – > Exit, this must close the designer    

2). Desktop Intelligence:

  Test Case Expected Results Actual Result Date Tested
31 Opening the Desktop Intelligence Tool Click on the Desktop Intelligence icon and it opens the reporter    
32 Login Login to the Desktop Intelligence Tool with correct user name and password    
33 Report File Name File Name should not contain any  Spaces and should be in lower Case    
34 Opening the report Double clicking opens the report    
35 Data Provider Are all data providers pointing to the appropriate environment (production or test)?    
36 Click on refresh data icon Report must run and data has to be refreshed    
37 Column Headers As specified by Client or logical name defining the values in the column.    
38 Report Title Title of the must be given for required reports    
39 Report Design Verify the universe location with connection parameters to make sure report is pulling data from right source.    
40 Report Format Report should not increase outside width of screen, but scrolling down is acceptable.    
    Date Formats according to requirements    
    There should not be any hidden objects in reports.    
    The report header must repeat for all report pages.    
41 New Report Click File-> New, the universe list must open    
42 Select Universe Select any one of the universe and it must take to query page    
43 Classes and Objects Double Click on the objects required, this must got to the results pane    
    Drag the required object and  it should go to the conditions pane    
    Click on the objects in conditions pane and the objects and classes pane changes to operators pane    
    Click on the required operator and the operators pane changes to operands pane    
44 Running the report Click on ‘Run’ button and report must be generated    
45 Save As The report must be saved in .rep format    
46 Save as excel The report must be saved in .xls format    
47 Scheduling the report  Click on File → Export to Repository-> Schedule, give the proper inputs for schedule and click OK.    
48 Exiting Desktop Intelligence Click on File → Exit the reporter must close.    

3. CMS ( Central Management Server): 

  Test Case Expected Results Actual Result Date Tested
49 Opening the CMC Click on the below URL and it opens the CMS    
50 Login Login to CMS with appropriate credentials and it takes you o the home page    
51 Click on users and groups Opens the users and groups page    
51 Click on create new user icon Opens the new user form page    
52 Creating a new user Give the required data to create a new user and click OK, this must create anew user    
53 Got to Servers page All the servers state must be ‘Running’    
54 Exiting CMS Click on Log Out button, the application logs out  and the login screen appears again    

4). Infoview: 

  Test Case Expected Results Actual Result Date Tested
55 Opening the Infoview Click on the URL and it opens the Infoview     
56 Login to Infoview Provide the required credentials and it opens the home page    
57 Opening Document List Click on Document List, New → Desktop Intelligence Document, this opens the  Desktop Intelligence Tool    
    Click on Document List, New → Web Intelligence Document, this opens the  available universe list    
58 Creating a Report from  Desktop/ Web Intelligence Select the universe and create a report and save the report    
59 Viewing My Inbox Saved report must be present in My inbox    
60 Exiting the Infoview Click on Log Out button, the application logs out  and the login screen appears again