Project Progress (Day-15)

Following test cases for  New User Creation page were made -

38	TC_New_User_038	New User	Verify lenght(6) of Zip textfield
39	TC_New_User_039	New User	Verify form of password and confirm password
40	TC_New_User_040	New User	Verify password and confirm password text field with numerics(0-9)
41	TC_New_User_041	New User	Verify password and confirm password text field with alphabets(a-z)
43	TC_New_User_043	New User	Verify password and confirm password text field with special characters
43	TC_New_User_043	New User	Verify minimum lenght(6) of password and confirm password textfield
44	TC_New_User_044	New User	Verify minimum lenght(6) of password and confirm password textfield
45	TC_New_User_045	New User	Verify minimum lenght(6) of password and confirm password textfield

Project Progress (day-14)

Following test cases for  New User Creation page were made -

29	TC_New_User_029	New User	Verify minimum lenght(10) of telephone textfield
30	TC_New_User_030	New User	Verify maximum length (13) of telephone text field
31	TC_New_User_031	New User	Verify maximum length (13) of telephone text field
32	TC_New_User_032	New User	Verify maximum length (13) of telephone text field
33	TC_New_User_033	New User	Verify Zip text field with numerics(0-9)
34	TC_New_User_034	New User	Verify Zip text field with alphabets(a-z)
35	TC_New_User_035	New User	Verify Zip text field with special characters
36	TC_New_User_036	New User	Verify lenght(6) of Zip textfield
37	TC_New_User_037	New User	Verify lenght(6) of Zip textfield

Project Progress (Day-13)

Following test cases for  New User Creation page were made -

16	TC_New_User_016	New User	Verify name text field with special characters
17	TC_New_User_017	New User	Verify minimum lenght(2) of name textfield
18	TC_New_User_018	New User	Verify minimum lenght(2) of name text field
19	TC_New_User_019	New User	Verify minimum lenght(2) of name text field
20	TC_New_User_020	New User	Verify maximum length (25) of name text field
21	TC_New_User_021	New User	Verify maximum length (25) of name text field
22	TC_New_User_022	New User	Verify maximum length (25) of name text field
23	TC_New_User_023	New User	Verify format of “Email” text field
24	TC_New_User_024	New User	Verify Telephone text field with numerics(0-9)
25	TC_New_User_025	New User	Verify telephone text field with alphabets(a-z)
26	TC_New_User_026	New User	Verify telephone text field with special characters
27	TC_New_User_027	New User	Verify minimum lenght(10) of telephone textfield
28	TC_New_User_028	New User	Verify minimum lenght(10) of telephone textfield

Project Progress (day-12)

Following test cases for  New User Creation page were made -

8	TC_New_User_008	New User	Verify minimum lenght(6) of username textfield
9	TC_New_User_009	New User	Verify minimum lenght(6) of username text field
10	TC_New_User_010	New User	Verify minimum lenght(6) of userfname text ield
11	TC_New_User_011	New User	Verify maximum length (20) of username text field
12	TC_New_User_012	New User	Verify maximum length (20) of username text field
13	TC_New_User_013	New User	Verify maximum length (20) of username text field
14	TC_New_User_014	New User	Verify Name text field with alphabets(a-z)
15	TC_New_User_015	New User	Verify name textfields with numerics(0-9)

Project Progress (Day-11)

Following test cases for  New User Creation page were made -

1	TC_New_User_001	New User	Verify the functionality of “New User” link
2	TC_New_User_002	New User	Verify the availablility of all the fields.
3	TC_New_User_003	New User	Mandatory fileds
4	TC_New_User_004	New User	Mandatory fileds
5	TC_New_User_005	New User	Verify Username text field with alphabets
6	TC_New_User_006	New User	Verify username textfields with numerics(0-9)
7	TC_New_User_007	New User	Verify Username text field with special characters

Project Progress(day-10)

Following test cases for  User Detail page were made -

1

TC_User_Details_001

User Details

Verify availabliity of selected page

Following test cases for Edit User page were made -

1	TC_Edit_User_001	Edit User	Verify the functionality of “Edit my profile”.
2	TC_Edit_User_001	Edit User	Verify the availability of “update” button
3	TC_Edit_User_003	Edit User	Verify the functionality of “update” button
4	TC_Edit_User_004	Edit User	Verify the availability of “save” button
5	TC_Edit_User_005	Edit User	Verify the functionality of “save” button
6	TC_Edit_User_006	Edit User	Verify the availability of “cancel” button
7	TC_Edit_User_007	Edit User	Verify the functionality of “cancel” button

Project Progress (day-9)

Following test cases for View User page were made -

1	TC_View_user_001	View_user	Verify the functionality of “View user” link
2	TC_View_user_002	View_user	Verify the functionality of “User name Coulmn”
3	TC_View_user_003	View_user	Verify the functionality of “Project” coulmn
4	TC_View_user_004	View_user	Verify clickablility of user name

Project Progress (day-8)

Following test cases for home page were made -

1	TC_Home_Page_001	Home_page	Verify that home page should be displayed after login
2	TC_Home_Page_002	Home_page	Verify the availability of list of tasks on home page
3	TC_Home_Page_003	Home_page	Verify the display of Username throughout the appliaction
4	TC_Home_Page_004	Home_page	Verify the availability of all the links

Project Progress (Day-7)

Following test cases for login- logout module were made -

11	TC_login_logout_011	Login-logout	Verify maximum length (20) of username text field
12	TC_login_logout_012	Login-logout	Verify maximum length (20) of username textfield
13	TC_login_logout_013	Login-logout	Verify maximum length (20) of username text field
14	TC_login_logout_014	Login-logout	Verify minimum lenght(6) of password
15	TC_login_logout_015	Login-logout	Verify minimum lenght(6) of password
16	TC_login_logout_016	Login-logout	Verify minimum lenght(6) of password
17	TC_login_logout_017	Login-logout	Verify maximum length (20) of password
18	TC_login_logout_018	Login-logout	Verify maximum length (20) of password
19	TC_login_logout_019	Login-logout	Verify maximum length (20) of password
20	TC_login_logout_020	Login-logout	Verify avaliablity of logout button
21	TC_login_logout_021	Login-logout	Verify the functionality of logout button
22	TC_login_logout_022	Login-logout	Verify the relogin using back button after logout

Project Progress (day-6)

Following test cases for login- logout module were made -

1.Verify login functionality with valid credentials

2.verify login functionality with invalid credentials

3.verify login functionality with invalid credentials

4.verify login functionality with invalid credentials

5.verify login functionality with invalid credentials

6.verify login functionality with invalid credentials

7.verify login functionality with invalid credentials

8.Verify minimum lenght(6) of username textfield

9.Verify minimum lenght(6) of username text field

10.Verify minimum lenght(6) of username textfield

project progress (day-5)

TEST DESIGN

Test Design is the phase to convert the Test Objectives into clear and visible Test Cases, Test Data, and Test Conditions.

Test Cases :

A test case in software engineering is a set of conditions or variables under which a tester will determine whether an application or software system is working correctly or not. Test Case is usually the smallest unit of  testing that are commonly used to determine whether an application or software system is working correctly or not as per the requirements or standards.

Detailed Information about the Test cases:-

A well-written test case ideally contains the following:

·         Test Name Or Test case ID : A unique ID assigned to every test case for easy identification.

·         Title Or Summary : Summary Provides the brief description about the condition to be tested.

·         Test Description : Test description provides the detailed description about the condition to be tested.

·         Test Priority : Prioritization of the test cases and based on this we would need to execute the test cases against new application instances/ build.

·         Test Data : Data used for performing the defined test.

·         Module / Feature Name : This field provides the name of the module to which the particular test case belongs.

·         Prerequisites : Any pre-conditions or requirement which is required to perform a particular test.

·         Test Steps : This is very important part in Test Case because it gives the clear picture what you are doing on the specific object.

·         Expected Result : This is the result of the above action. It specifies what the specification or user expect from that particular action.

·         Test Environment : Environment in which testing is performed (for example on different browsers or Operating systems).

project progress (Day-4)

   TEST APPROACH/ STRATEGY

QA will use the Alprus FRS for performing the functionality testing. Basic focus of testing will be on task functionality and usability testing. The following details the type of testing applied to this application.

·         Functionality testing

·         Compatibility testing

·         Usability testing

·         Regression testing

      BUILD PLAN AND TEST ENVIRONMENT CONFIGURATION

QA will be notify of the new build deployed on QA environment so that QA can regress the   fixed defect and perform testing on the new implemented or blocked areas in the application.

Alprus development team will update QA team along with release notes once the new build has been deployed on QA environment (TBD)

OS / Browsers  compatibility matrix.

OS                                             BROWSER	IE 6.0	IE 7.0	Firefox 2.0	Safari
Window vista	NA	Supported	Supported	NA
Window XP	Supported	Supported	Supported	NA
Macintosh OSX	NA	NA	Supported	Supported

      DEFECT TRACKING

Defect tracking will be done through a centralized bug tracking system.

QA will be reporting all the defects in bug base related to Alprus under one predefined project.

                  ENTRY AND EXIT CRITERIA

QA team will be reporting the defect during the Alprus and project team management will be deciding about the releasing the application to the market.

                         COMMUNICATION PLAN

Bug will be reported in an online bug tracking system. Once the testing starts , a clear escalation path will be defined to ensure timely resolution of the issues(TBD).

                     RISK

Smooth execution of the testing plans will be dependent on following:

a.       Development teams timely input.

b.      New build in time as per plan.

c.       Minimal downtime of Alprus application which Minimizes testing time.

d.      Availability of hardware resources to perform the testing.

e.       Timely fixing the bugs to perform the regression testing.

f.       Critical bugs, which may impact the complete testing of the application, be fixed right always.

g.      Bug base to  have minimal downtime.

    ASSUMPTIONS

QA team will not be executing any other test cases at the time of  Fixed Bugs Regression.QA team will only  be doing the regression of the bugs that have been fixed.

QA team will not be testing any areas/ features which are not defined in the project scope of the   testing.     

Project progress (day-3)

  FEATURES TO BE TESTED

Alprus Features List : Following lists the high level features available in Alprus application.

1.                   Login/Logout Functionality.

2.                  Alprus Homepage

3.                  Super Admin Administrator

4.                  User page

5.                  User Detail page

6.                  Edit user Detail Page

7.         Task Page

8.         Task creation

9.         Editing task Details.

10.       Task Assignment.

        i.            Login\Logout Functionality:

User is only allow to login to the application after validating the providing valid credentials. Logout functionality will be logging out the user from the application. Also user should not be able to login again after having logged out from the application.

User created by another user should able to application using the credentials provided by the creator.

     ii.            Alprus Homepage:

 Once the user login to the application, the  user will see the homepage first . Home page should list all the tasks assigned to that user .Homepage will display the welcome message for the user. There will be links available on Top left comes for navigating to home. Tasks and users pages and this section will be header section. Logout link will be existing on the right hand side of the header. Clicking  Home link will take the user to Home page of the application .Similarly clicking Task will navigate to the User  page.

    iii.            Super Admin Administration:

There is one Super Admin in the application that can perform every action in the application. Super Admin can create other users in the application. Also Super Admin can create tasks in the application and can assign tasks to different users.

    iv.            User Page:

User  page will be having all the users in the application .Any logged in user can reach users page by clicking users link on top left comes of the application ”User name” column on users page will display the First name , last Name of the User as a section to select the user. Clicking on First Name,  Last Name of the user section will select the users from User’s page the logged in user can create the new user in the application using the “New User” option. Also from the users page the logged in user can view the details of the selected users. However clicking open without selecting the user should display a massage to select the user first. User’s page is also have the “Edit ” option to edit the detail of the selected user. In the same manner as in new user case, clicking edit without selecting the user should display the message to select the user first.

      v.            User Detail Page:

User detail page can be reached for the selected user by clicking Open option available on the user page.User detail page will only display the details added by the user during the New User Creation.

    vi.            Edit User Details:

Clicking edit on user page allow the user to Edit User Details of the selected user.

Clicking Save button on Edit user page will save the updated details of the user and clicking the cancel button will not save the details and will take the user back to the user page.

  vii.            New User Creation:

Any user can create a new user in the application by clicking the ”New User” link on the user page. Clicking “New User ” link will take the user to New User Page where user will provide following field for the new user :

1.                  User name

2.                  First name

3.                  Last name

4.                  Email

5.                  Address

6.                  City

7.                  State

8.                  Country

9.                  Phone

10.              Zip

Clicking save button on this page will save the details and create a user and clicking the Cancel button on New User page will take the user back to the User page without saving the details.

viii.            Task Page:

User can reach Task Page by clicking the Task link on the Top left corner of the page . Task page will list all the task created in the application by any user “Task name” column as Task page will display all the task of the Task.

Task Page should have three options, one for creating new task , second for Edit Task and third for assigning Task.

    ix.            Task Creation:

User can create a new task in the application by clicking “New Task” link on the Task page. Clicking “New Task” will take the user to new task page where user will provide task name and description of task.

After   clicking ‘Save Button” on the new task page will save the detail and create a new task. However if the user click cancel button on new task page nothing will be saved and control navigates back to task page.

      x.            Editing Task Details:

After the user has created the task, the user can edit the detail about the task. User will need to select the task and Click “Edit Task” link to edit it. After editing the details if we click the ”Save” button on Edit Task page, the changes will save the updated in the task. However clicking Cancel button will not save the details and take the user back to the Tasks page.

   FEATURES NOT TO BE TESTED

Any feature, which are there in the project scope , but have not been developed by feature complete build , will need to be treated as exceptions and tracked accordingly. Features not in the project scope will also not be tested even if developed.

        i.            Assigning Tasks:

After a user has created a task, the created task can be assigned to any user by the task creator. User will need to select the task and click” Assign” button it should assign the selected task to the selected user and clicking the “Cancel” button should take the user back to the Task Page without assigning the task.

Project Progress (Day-2)

Test Planning and control

In this phase of STLC we use to create a Test Plan. Hence the Test Plan for our project is:

Quality  Assurance  Strategy  For  Alprus

Test Plan

  INTRODUCTION

This main objective of this test plan is to cover and document the features, areas and approaches to be used while testing Alprus product hence to formalize testing approach and test planning the main objectives of creating Test plan is to

1.                  Detail the “Task Assignment” process required to test the Alprus application.

2.                  Identify the resources required to complete the testing of this product.

3.                  Communicate that issues and defect associated with this product testing.

4.                  Identify the risk involved in the testing of the Alprus product.

  PROJECT OVERVIEW

This product involves testing the crucial areas where users can create and assigned different tasks as well as create new users. Alprus  is  a web interface for creating and assigning of tasks by the users to the users .Using this application users can create more users and can create / edit / assign the task to other users.

The application is a platform for students training on learns about testing, test cases execution, finding bugs and verifying fixed bugs and learns QA  processes.

      RELATED DOCUMENT

The following is a list of  known documents to aid is Testing.

·         PRD

·         Alprus FRS .doc

·         User Interface screen shots.

·         Database Design doces.doc.

·         Development schedule.mpp

     SCOPE

The Scope of the testing of Alprus project involves testing creation of Users and  tasks as well as editing of created users and task.

Scope of testing involves testing the Alprus application from functionality stand-point of view. This is the first version of the application so there is no migration of data involved in it, hence no migration testing. Initially this application is oriented of 40 users ,so no load testing will be performed on the application .QA will not be performing any installer testing on this application as it's  a web based application and QA is using the URL of the application for testing it.QA will be testing the features in the application as mentioned in the mentioned in the section features to be tested. QA  will be performing fixed bugs regression when development team fixed the bugs in the application.QA will be performing the integration testing of different module of the Alprus application to ensure that all the module are working fine. QA  will be performing the testing of the application with admin users as well as with normal users of the application.