Lmt Overview Scenarios

Modules for the LMT: 1. Admin Login 2. Add User 3. Dynamic Navigation: Add Menu Category, List Menu Category, Edit Menu Category 4. Lead Master: Create Lead, New Contact, Contact Info, Address Info, Save Info 5. Forecasts of the Projects 6. Cases of the Projects 7. Document Library 8. Project Report 9. Document Recycle Bin 10. Individual Dash Boards

Test Scenario's: 1. Admin Login: The Valid Username and Password will be redirected to the respective User page Test Scenario 1: User name input object

Login Page (Admin Login) Test Scenario 1: Username Input Object Test Scenario 2: Password Input Object Test Scenario 3: Submit Button Test Scenario 4: Clear Button Test Scenario 5: Forgot Password Test Scenario 1: Username BVA: It should accept only Characters Min 4 Max 16 and Numerics 0 to 9 It should not accept Spl Char and Space It is a mandatory field Test Scenario 2: Password It should accept Characters, Numerics and special characters Min 8 Max 10 It is a mandatory field Entered characters should be encrypted

Test Scenario 3: Submit Button The Submit button should accept only when the above two fields are valid if not should not Accept Test Scenario 4: Clear Button The fields should remain empty when we click on clear button Test Scenario 5: Forgot Password Forgot the password then the user has to answer the hint question and if it is

correct then his

password will be displayed after giving his username.

2. Add User: The admin user page will be loaded with a hyperlink “Add User” for adding a new user to the  database. The Add User Hyperlink click event will display the below identified objects. All the inputs are  mandatory Test scenario 1: Full name  Test scenario 2: User name Test scenario 3: Password Test scenario 4: Email Test scenario 5: User type (Drop down) Admin/Staff Test scenario 6: Hint question Test scenario 7: Hint Answer Test scenario 8: Add Button Test scenario 9: Clear Button Test scenario 10: Cancel Button Test scenario 1: Full name­ The input object should accept characters between 5 and 35 BVA:  1. It should accept min 5 chars and max 35 chars 2. It should not accept less than 5 and greater than 35 chars 1

3. It should not accept spaces, Spl. Chars, numeric’s in the beginning of the full name

Test Scenario 2: User name­ The input object should accept characters between 4 and 10 BVA:  1. It should accept min 4 chars and max 10 chars 2. It should not accept less than 4 and greater than 10 chars

1

3. It should not accept spaces, Spl. Chars, numerics in the begining of the User name

Test scenario 3: Password­ The password given by the Admin user will give a pre­designed alphanumeric of fixed size of 6 chars Test scenario 4: Email­ The official email id of the new user should be entered in input object by the admin user. The email id format ex: “[email protected]” It should not accept any inputs if the mailed format is differs from the above given format. Test scenario 5: User type (Drop down)­ Admin/Staff  The Admin user will select the user type based on the user domain/thier activities. The type selection is a dropdown option in which one selection is possible out of 2 available options (Admin  group or Staff) Test scenario 6: Hint question­ The hint question hyperlink click event will provide a set of questions as drop down user has to select one question from the drop down list.   Test scenario 7: Hint Answer­ The hint answer hyperlink click event will provide a set of answers as drop down user has to select one from the drop down Test scenario 8: Add Button­ The Add button click event will check for all the mandatory values. If all the required inputs available then  an alert displays as”User added successfully” If necessary inputs not available an alert displays as “Please Enter the required information” Test scenario 9: Clear Button­ The Clear button click event will refreshes the current page and appears with blank input objects Test scenario 10: Cancel Button­ The Cancel button will close the active window 3. Dynamic Navigation: Add Menu Category

Test Scenario 1: Menu click­  The click event will provide a list of predefined items. The Add item should be available

Test Scenario 2: The Add click­ This click event will open a new window. The input object should accept min 4 and max 8 chars

LIST MENU CATEGORY (Dynamic Navigation) Test Scenario 1: Click on Hyperlink After click on to Hyperlink the Listed items should be displayed

EDIT MENU CATEGORY (Dynamic Navigation) Test Scenario 1: Click on any one of the listed item Test Scenario 2: Input Box Test Scenario 3: Save Test Scenario 4: Cancel Test Scenario 1: Click on any one of the listed item When we click on any one of the listed item the input window should appear Test Scenario 2: Input Box It should accept Min 5 and Max 35 characters only Test Scenario 3: Save The entered data should be saved Test Scenario 4: Cancel If we click on cancel button the listed items should be cancelled.

4. Lead Master: Create Lead­ In General for each Customer one Lead is allotted. Through lead master the Admin User will assign a lead to each Customer. Test Scenario 1: Customer selection­

The   drop   down   consists   of   list   of   available   customer's.     The   customer   item   selection   will   provide   their  respective Lead, if exists. If Lead not exists for any customer, a new Lead to be create for the respective customer

Test Scenario 2: Lead Selection­ The Lead drop down will provide list of Lead members, from that list one of the Lead to be assigned to  respective customer by selecting from the list items Lead New Contact: Test scenario 1: Full name­ Test Scenario 1: User Test Scenario 2: New user Test Scenario 3: Yes or No Test Scenario 4: Add Contact Test Scenario 2: New user It should display some existing contacts in a separate window with yes or No Test Scenario 3: Yes or No Before creating a contact, first we have to check whether there is any contact which is Already in the list or he is a repeating customer Id [using process field is Y or N] Test Scenario 4: Add Contact If yes then we do not create new contact and will create this contact under the same existing customer profile as a new job-work. If No then we will create a new contact. Test Scenario 1: User

The input object should accept characters between 5 and 35 Click on the User button BVA:  1. It should accept min 5 chars and max 35 chars

2. It should not accept less than 5 and greater than 35 chars             3. It should not accept spaces, Spl. Chars, numeric’s in the beginning of the full name 4. The official email id of the new user should be entered in input object by the admin user. The email id format ex: “[email protected]” 5. It should not accept any inputs if the mailed format is differs from the above given format.

Lead Contact Info: Test Scenario 1: Lead selection

Selection of the lead member item from drop down, will provide the contact info. For the respective Lead. Lead Address Info: Test Scenario 1: Selection of Lead From drop down list box               The lead address and contact information will be displayed in the same page                Lead Save Info: Test Scenario 1: Button click The button click event will display an alert of “Record Updated” 5. Forecasts of the Projects:  The project status can be forecast for the next Quarter, Half year or annual. Test Scenario 1: Button click The button click event will open a new window in a report format for the existing project forecasts 6. Cases of the Projects:  This is to check for existing clients and new relationships for the projects and its details in the organization from the defined customers table. 7. Document Library: 1. Test Scenario 1: Search Button 2. Test Scenario 2: Save Button 3. Test Scenario 3: Cancel Button 4. Test Scenario 1: Search Button 5. This search button searches for the existing of projects/products catalog brochures, corporate literature, templates, and logos in the Documents Library page for the members in the project. 6. Enter the matter you want to search in the search box(for example:- products catalog brochures) ,and click on the search button. This search button enables users to quickly retrieve relevant documents. 7. Test Scenario 2: Save Button 8. After searching the required document , if found the document, Click on the save button. The required document is saved, else it should the message that the data not found. 9. Test Scenario 3: Cancel Button

10. If you want to cancel the search, then click on the cancel button. Cancel the selected options by the user and this should be privileged by project manager.

Test Scenario 1: Button click The button click event will open a new window in a report format for the existing projects details for the respective customer detals 8. Project Report: This is to check for existing and completed status of projects/products reports by the Project Manager, Project Leads, Team Leads, and Sales/Business Development Reports as well.

Test Scenario 1: Button click The button click event will open a new window in a report format about information for all the existing projects 9. Document Recycle Bin: This is to delete or undelete the existing and completed status of projects/products documents that are unnecessary.

Test Scenario 1: Button click A message is displayed with the project description and status of the project is to be displayed existing or if data is not present then it should display a message as user data is not found. 10. Individual Dash Boards: Here we can share our Information to the Project Team Members overall we can have Individual Dash Baord, Administrated by the Administrator Test Scenario 1: Button click A message is displayed with the project description and status of the project is to be displayed existing or if data is not present then it should display a message as user data is not found