SlideShare a Scribd company logo
1 of 14
Mainsaver 8.300 Upgrade Functional Testing
Documentation
Mainsaver 8.30 And Web Request 8.300
Functional Testing And Documentation
Scott M Queen
Scott Queen 1
Mainsaver 8.300 Upgrade Functional Testing Documentation
1. TEAM LEADER/MEMBER RELATED FUNCTIONAL TESTS....................................3
Mainsaver 8.300 Upgrade Functional Testing Documentation
1. Team Leader/Member Related Functional Tests
This test document records the tests that have been conducted on MainSaver 8.30 in the test
database were conducted by the testing group in the Facilities/Corporate Division. The main
type of testing included:
Team Leader/Member Related Functional Tests.
This team included project leader: Scott Queen and group members: Salvatore Monaco,
Dennis Palumbo, and Joe Fazio.
Contact: Scott Queen for further information on the testing.
Mainsaver 8.300 Upgrade Functional Testing Documentation
1.1.1 Test case “9588 PM Edit Bug Fix”
1.1.1.1 Test Description
PM Edit - using the UP/DOWN arrow keys in the work requested field scrolls to the next PM
record. This is a known bug that was fixed in version 8.3.100.
1.1.1.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to Preventative Maintenance Module.
• Execute actions
• Select the PM iconic button from the main screen array.
• Click on the Retrieve button.
• Define query in the drop down list.
• Click on one of the pm records retrieved.
• It will open into the selected detailed view (this is the fix).
• Close record when completed viewing.
• This completes the verification of the documented 9588 bug fix.
Expected results:
• The correct query item is opened when clicked upon.
Signature Scott M Queen Date: 11/2014
1.1.2 Test case “8638 Printable Report of Application Security Settings”
1.1.2.1 Test Description
Test enhancement in the system administration module that allows system admin to print a
reports of all user access levels and other security settings for audits.
1.1.2.2 Procedure
Prerequisites
• Login To Mainsaver Testing DB
Actions
• From main menu select system administration module.
Mainsaver 8.300 Upgrade Functional Testing Documentation
• Enter system credentials to login to module *Note only (1) admin has accesses to this
module.
• Select the reports option
• There are three printable reports to choose from “User Groups And members”,” Login Id
And Groups”,” Application Security By user”
Expected results
• This will enhance application performance in organizing and setting application security
and for future possible audits.
Signature Scott M Queen Date: 11/2014
1.1.3 Test case “9382 Move Columns Display”
1.1.3.1 Test Description
To give the capability to move columns around and sort data per user and for the columns to
remain where the user places them.
1.1.3.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• From the main menu select the Materials module.
• Execute actions
• Click on parts master button
• Click on “file”
• Click “order point review”
• Right click on one of the columns and move it besides another column and let go.
Expected results
• The column will move to its new set location and will remain there.
Mainsaver 8.300 Upgrade Functional Testing Documentation
Signature Scott M Queen Date: 11/2014
1.1.4 Test case “9433 Using “In” Operator in Face Queries”
1.1.4.1 Test Description
Can not use the search operator “In” when doing a query in groups. Example a search of the
following: Next Create Date: >= 10/10/2005 and Planner: In: (‘22072’,’901531’) Returns Ora-
00907 missing right parenthesis.
1.1.4.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to Preventive maintenance module
• Click Pm button
• Click Retrieve
• Click Define Query
• Select “Next Create Date”
• Select operator “like”
• Enter in a date 00/00/00
• Select marker to add a new command line.
• Select “Planner” operator “in”
• Group the following type in (‘22072’,’901531)
• Click OK
Expected results:
• Information that was queried was retrieved with out Ora-00907 message and information
was correct.
Signature Scott M Queen Date 12/2004
1.1.5 Test case “9390 Order Point Missing Decimal”
1.1.5.1 Test Description
Decimal Part of suggested order qty is cut out of report.
1.1.5.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to Maintenance Module
Mainsaver 8.300 Upgrade Functional Testing Documentation
• Click Parts Master
• Click Reports
• Select order point report
• Once query box appears “Select all Records” check box
Expected results:
• The decimal is not cut off.
Signature Scott M Queen Date 12/2004
1.1.6 Test case “8942 Order Point Separation Line”
1.1.6.1 Test Description
Add separator line between suppliers on the order point report. Currently there is no
divider.
1.1.6.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to materials module c
• Click “Parts Master”
• Select “order point report”
• Once the query box comes up select the “select all records” option
• View the report on screen
• Click the “Print” button on bottom right hand screen.
• Add/edit/delete new activity version and information
Expected results:
• The separation line was printed and viewed on screen.
Signature Scott M Queen Date 12/2004
Mainsaver 8.300 Upgrade Functional Testing Documentation
1.1.7 Test case “9202 Asset Entry Not Required For Web Request”
1.1.7.1 Test Description
Asset entry is an optional field and is not required when a user is submitting a work
request.
1.1.7.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to mainsaver web request Http://workreq
• Select “Submit New Request”
• Submit screen appears Fill in Required information items are in red.
Expected results:
• Asset number is not in red therefore not a required item.
Signature Scott M Queen Date 1/2005
1.1.8 Test case “8802 Reset Table View Column”
1.1.8.1 Test Description
Have an option to reset the view of a table if a user changes it.
1.1.8.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Mainsaver 8.300 Upgrade Functional Testing Documentation
Actions
• Navigate to maintenance module
• Execute actions
• Select “Work Order” button
• Select “Define Query” button
• When query box comes up select “All Records” check box
• Select “options” in the top toolbar
• Select “Reset Table View Column”
Expected results:
• Restored table view to previous settings
Signature Scott M Queen Date 11/2004
1.1.9 Test case “4621 Mass Close Purchase Orders”
1.1.9.1 Test Description
Add option of mass close purchase orders.
1.1.9.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to Purchasing module
• Execute actions
• Click on “Purchase Order”
• Click on “Retrieve Query”
• Select the date range you wish to go back to.
• Once search results come back go to “File”
• Select “Mass-Close Po”
Expected results:
• Closed out all Po’s that where in table view.
Signature Scott M Queen Date 1/2005
Mainsaver 8.300 Upgrade Functional Testing Documentation
1.1.10 Test case “5595 Using PDF’s With PM References”
1.1.10.1 Test Description
The ability to now use PDF forms and attach them to a Pm reference tab.
1.1.10.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to Pm module
• Execute actions
• Click on Pm record you want to attach PDF forms.
• Under the “References Tab” select “Add”
• Input file name into references box.
• Click OK
• Next time the Pm is generated it will print the pdf.
Expected results:
• Can now Print out PDF forms.
Signature Scott M Queen Date 1/2005
Mainsaver 8.300 Upgrade Functional Testing Documentation
1.1.11 Test case “5953 Add Pm Id Number to Preventive Maintenance Work Order”
1.1.11.1 Test Description
Add the Pm Id number to the Preventive Maintenance work order when it is generated.
1.1.11.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• No action needed. It automatically prints on the preventive maintenance work order.
Expected results:
• Pm Id is reflected on the preventive maintenance work orders.
Signature Scott M Queen Date 11/2004
1.1.12 Test case “939 print A Work Order From Web Request Module”
1.1.12.1 Test Description
To be able to print a work order once it has been changed from a request into a work
order at the request screen.
1.1.12.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Click on Maintenance module
• Click on the “Work Req” button
• Click on “Retrieve Query” button
• From the drop down arrow select “Pending Request”
• Double click on a request
• Enter the asset number that the request will be assigned to
• Click OK
• Once you are back to the “Pending Request” Screen select the request you just
changed.
• Click “Review” button on the toolbar
Mainsaver 8.300 Upgrade Functional Testing Documentation
• Click the “Approve” Button that appears on the bottom right hand corner.
• The A status box will appear select the status code “Do” ready to be done like in
previous version
• Once that is selected check the check box below the status field that says “Print
Work Order” This is the new feature that allows you to by-pass going to the work
order module to print the work order.
Expected results:
• Printed the assigned work order from web request.
1.1.13 Test case “9099 Add Option Fields to Work Request Module”
1.1.13.1 Test Description
Add the option fields that exist in the work order module to the request module so
approvers can enter miscellaneous information via the request module.
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to Maintenance Module
• Click on the “Work Req” button.
• Go to “New”
• You will see the (5) option fields and (2) date fields like the ones that exist in the
work order module.
Expected results:
• The fields do exist in the work request new screen.
Signature Scott M Queen Date 12/2004
Mainsaver 8.300 Upgrade Functional Testing Documentation
1.1.14 Test case “9302 Changing Password Using Special Characters”
1.1.14.1 Test Description
To be able to use special characters in a user password.
1.1.14.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to “System Administration Module”
• Select a user name
• Manually change the password and include special characters.
Signature Scott M Queen Date 1/2005
Mainsaver 8.300 Upgrade Functional Testing Documentation
1.1.15 Test case “9634 Can Not Automatically Enter In A Asset Number On The Fly”
1.1.15.1 Test Description
Can not automatically add an asset “on the fly” via the Pm module
1.1.15.2 Procedure
Prerequisites
• Login to MainSaver Testing DB
Actions
• Navigate to “Preventive Maintenance Module
• Execute actions
• Click on “Pm” button
• Select “New” button
• When you type in an asset that does not exist in database it will prompt you if you
want to add it.
Signature Scott M Queen Date 1/2005
One SOP did change with this upgrade. A manual was made explaining the new option
available in the work request section. Reference “939 Print A work Order from Web request”
This was sent out on 01/24/2005 and all so made available on a group shared folder for
Mainsaver.

More Related Content

What's hot

Application Catalog and Approval Runbooks Sample
Application Catalog and Approval Runbooks SampleApplication Catalog and Approval Runbooks Sample
Application Catalog and Approval Runbooks SampleJames Donnelly
 
ApplicationTestPlan[1]
ApplicationTestPlan[1]ApplicationTestPlan[1]
ApplicationTestPlan[1]Minu Mishra
 
Performance and load testing
Performance and load testingPerformance and load testing
Performance and load testingsonukalpana
 
ELW_Symantec_SD 7 1 Upgrade and Install_Draft1_Charles_edited
ELW_Symantec_SD 7 1 Upgrade and Install_Draft1_Charles_editedELW_Symantec_SD 7 1 Upgrade and Install_Draft1_Charles_edited
ELW_Symantec_SD 7 1 Upgrade and Install_Draft1_Charles_editedElizabeth Wilcox
 
Autodesk Updates and Hotfixes
Autodesk Updates and HotfixesAutodesk Updates and Hotfixes
Autodesk Updates and HotfixesJerome Castañeda
 

What's hot (6)

Application Catalog and Approval Runbooks Sample
Application Catalog and Approval Runbooks SampleApplication Catalog and Approval Runbooks Sample
Application Catalog and Approval Runbooks Sample
 
ApplicationTestPlan[1]
ApplicationTestPlan[1]ApplicationTestPlan[1]
ApplicationTestPlan[1]
 
Performance testing
Performance testingPerformance testing
Performance testing
 
Performance and load testing
Performance and load testingPerformance and load testing
Performance and load testing
 
ELW_Symantec_SD 7 1 Upgrade and Install_Draft1_Charles_edited
ELW_Symantec_SD 7 1 Upgrade and Install_Draft1_Charles_editedELW_Symantec_SD 7 1 Upgrade and Install_Draft1_Charles_edited
ELW_Symantec_SD 7 1 Upgrade and Install_Draft1_Charles_edited
 
Autodesk Updates and Hotfixes
Autodesk Updates and HotfixesAutodesk Updates and Hotfixes
Autodesk Updates and Hotfixes
 

Similar to Validation.Document.Sample

Mercury Testdirector8.0 using Slides
Mercury Testdirector8.0 using SlidesMercury Testdirector8.0 using Slides
Mercury Testdirector8.0 using Slidestelab
 
Performance testing with Jmeter
Performance testing with JmeterPerformance testing with Jmeter
Performance testing with JmeterPrashanth Kumar
 
Acceptance Testing Practical Guideline.pptx
Acceptance Testing Practical Guideline.pptxAcceptance Testing Practical Guideline.pptx
Acceptance Testing Practical Guideline.pptxShaikh848892
 
Quality Center
Quality CenterQuality Center
Quality CenterSachin-QA
 
Test Management Tool HP ALM- Quality Center Part 1
Test Management Tool  HP ALM- Quality Center Part 1Test Management Tool  HP ALM- Quality Center Part 1
Test Management Tool HP ALM- Quality Center Part 1Murageppa-QA
 
HP Quality Center
HP Quality CenterHP Quality Center
HP Quality CenterANKUR-BA
 
Test Management Tool HP ALM- Quality Center Part 2
Test Management Tool  HP ALM- Quality Center Part 2Test Management Tool  HP ALM- Quality Center Part 2
Test Management Tool HP ALM- Quality Center Part 2Murageppa-QA
 
Perfromane Test Tool jmeter
Perfromane Test Tool jmeterPerfromane Test Tool jmeter
Perfromane Test Tool jmeterNaga Mallala
 
Test cases and bug report v3.2
Test cases and bug report v3.2Test cases and bug report v3.2
Test cases and bug report v3.2Andrey Oleynik
 
Qa case study
Qa case studyQa case study
Qa case studyhopperdev
 
2F9_S4HANA2020_BPD_EN_US.docx
2F9_S4HANA2020_BPD_EN_US.docx2F9_S4HANA2020_BPD_EN_US.docx
2F9_S4HANA2020_BPD_EN_US.docxArun Obilisetty
 
Quick Test Professional (QTP/UFT)
Quick Test Professional (QTP/UFT)Quick Test Professional (QTP/UFT)
Quick Test Professional (QTP/UFT)Rajathi-QA
 
Moogilu qa-case study (Software Testing)
Moogilu qa-case study (Software Testing)Moogilu qa-case study (Software Testing)
Moogilu qa-case study (Software Testing)Jagadish Channagiri
 
Testing Frameworks
Testing FrameworksTesting Frameworks
Testing FrameworksMoataz Nabil
 

Similar to Validation.Document.Sample (20)

Mercury Testdirector8.0 using Slides
Mercury Testdirector8.0 using SlidesMercury Testdirector8.0 using Slides
Mercury Testdirector8.0 using Slides
 
Performance testing with Jmeter
Performance testing with JmeterPerformance testing with Jmeter
Performance testing with Jmeter
 
Acceptance Testing Practical Guideline.pptx
Acceptance Testing Practical Guideline.pptxAcceptance Testing Practical Guideline.pptx
Acceptance Testing Practical Guideline.pptx
 
Quality Center
Quality CenterQuality Center
Quality Center
 
Test Management Tool HP ALM- Quality Center Part 1
Test Management Tool  HP ALM- Quality Center Part 1Test Management Tool  HP ALM- Quality Center Part 1
Test Management Tool HP ALM- Quality Center Part 1
 
HP Quality Center
HP Quality CenterHP Quality Center
HP Quality Center
 
Test Management Tool HP ALM- Quality Center Part 2
Test Management Tool  HP ALM- Quality Center Part 2Test Management Tool  HP ALM- Quality Center Part 2
Test Management Tool HP ALM- Quality Center Part 2
 
Perfromane Test Tool jmeter
Perfromane Test Tool jmeterPerfromane Test Tool jmeter
Perfromane Test Tool jmeter
 
Test cases and bug report v3.2
Test cases and bug report v3.2Test cases and bug report v3.2
Test cases and bug report v3.2
 
Qa case study
Qa case studyQa case study
Qa case study
 
PEOPLESOFT PTF
PEOPLESOFT PTFPEOPLESOFT PTF
PEOPLESOFT PTF
 
HP ALM QC
HP ALM QCHP ALM QC
HP ALM QC
 
2F9_S4HANA2020_BPD_EN_US.docx
2F9_S4HANA2020_BPD_EN_US.docx2F9_S4HANA2020_BPD_EN_US.docx
2F9_S4HANA2020_BPD_EN_US.docx
 
Combined Project
Combined ProjectCombined Project
Combined Project
 
Quick Test Professional (QTP/UFT)
Quick Test Professional (QTP/UFT)Quick Test Professional (QTP/UFT)
Quick Test Professional (QTP/UFT)
 
Moogilu qa-case study (Software Testing)
Moogilu qa-case study (Software Testing)Moogilu qa-case study (Software Testing)
Moogilu qa-case study (Software Testing)
 
Testing Frameworks
Testing FrameworksTesting Frameworks
Testing Frameworks
 
Software automation
Software automationSoftware automation
Software automation
 
Front Cover:
Front Cover:Front Cover:
Front Cover:
 
Front Cover:
Front Cover:Front Cover:
Front Cover:
 

Validation.Document.Sample

  • 1. Mainsaver 8.300 Upgrade Functional Testing Documentation Mainsaver 8.30 And Web Request 8.300 Functional Testing And Documentation Scott M Queen Scott Queen 1
  • 2. Mainsaver 8.300 Upgrade Functional Testing Documentation 1. TEAM LEADER/MEMBER RELATED FUNCTIONAL TESTS....................................3
  • 3. Mainsaver 8.300 Upgrade Functional Testing Documentation 1. Team Leader/Member Related Functional Tests This test document records the tests that have been conducted on MainSaver 8.30 in the test database were conducted by the testing group in the Facilities/Corporate Division. The main type of testing included: Team Leader/Member Related Functional Tests. This team included project leader: Scott Queen and group members: Salvatore Monaco, Dennis Palumbo, and Joe Fazio. Contact: Scott Queen for further information on the testing.
  • 4. Mainsaver 8.300 Upgrade Functional Testing Documentation 1.1.1 Test case “9588 PM Edit Bug Fix” 1.1.1.1 Test Description PM Edit - using the UP/DOWN arrow keys in the work requested field scrolls to the next PM record. This is a known bug that was fixed in version 8.3.100. 1.1.1.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to Preventative Maintenance Module. • Execute actions • Select the PM iconic button from the main screen array. • Click on the Retrieve button. • Define query in the drop down list. • Click on one of the pm records retrieved. • It will open into the selected detailed view (this is the fix). • Close record when completed viewing. • This completes the verification of the documented 9588 bug fix. Expected results: • The correct query item is opened when clicked upon. Signature Scott M Queen Date: 11/2014 1.1.2 Test case “8638 Printable Report of Application Security Settings” 1.1.2.1 Test Description Test enhancement in the system administration module that allows system admin to print a reports of all user access levels and other security settings for audits. 1.1.2.2 Procedure Prerequisites • Login To Mainsaver Testing DB Actions • From main menu select system administration module.
  • 5. Mainsaver 8.300 Upgrade Functional Testing Documentation • Enter system credentials to login to module *Note only (1) admin has accesses to this module. • Select the reports option • There are three printable reports to choose from “User Groups And members”,” Login Id And Groups”,” Application Security By user” Expected results • This will enhance application performance in organizing and setting application security and for future possible audits. Signature Scott M Queen Date: 11/2014 1.1.3 Test case “9382 Move Columns Display” 1.1.3.1 Test Description To give the capability to move columns around and sort data per user and for the columns to remain where the user places them. 1.1.3.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • From the main menu select the Materials module. • Execute actions • Click on parts master button • Click on “file” • Click “order point review” • Right click on one of the columns and move it besides another column and let go. Expected results • The column will move to its new set location and will remain there.
  • 6. Mainsaver 8.300 Upgrade Functional Testing Documentation Signature Scott M Queen Date: 11/2014 1.1.4 Test case “9433 Using “In” Operator in Face Queries” 1.1.4.1 Test Description Can not use the search operator “In” when doing a query in groups. Example a search of the following: Next Create Date: >= 10/10/2005 and Planner: In: (‘22072’,’901531’) Returns Ora- 00907 missing right parenthesis. 1.1.4.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to Preventive maintenance module • Click Pm button • Click Retrieve • Click Define Query • Select “Next Create Date” • Select operator “like” • Enter in a date 00/00/00 • Select marker to add a new command line. • Select “Planner” operator “in” • Group the following type in (‘22072’,’901531) • Click OK Expected results: • Information that was queried was retrieved with out Ora-00907 message and information was correct. Signature Scott M Queen Date 12/2004 1.1.5 Test case “9390 Order Point Missing Decimal” 1.1.5.1 Test Description Decimal Part of suggested order qty is cut out of report. 1.1.5.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to Maintenance Module
  • 7. Mainsaver 8.300 Upgrade Functional Testing Documentation • Click Parts Master • Click Reports • Select order point report • Once query box appears “Select all Records” check box Expected results: • The decimal is not cut off. Signature Scott M Queen Date 12/2004 1.1.6 Test case “8942 Order Point Separation Line” 1.1.6.1 Test Description Add separator line between suppliers on the order point report. Currently there is no divider. 1.1.6.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to materials module c • Click “Parts Master” • Select “order point report” • Once the query box comes up select the “select all records” option • View the report on screen • Click the “Print” button on bottom right hand screen. • Add/edit/delete new activity version and information Expected results: • The separation line was printed and viewed on screen. Signature Scott M Queen Date 12/2004
  • 8. Mainsaver 8.300 Upgrade Functional Testing Documentation 1.1.7 Test case “9202 Asset Entry Not Required For Web Request” 1.1.7.1 Test Description Asset entry is an optional field and is not required when a user is submitting a work request. 1.1.7.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to mainsaver web request Http://workreq • Select “Submit New Request” • Submit screen appears Fill in Required information items are in red. Expected results: • Asset number is not in red therefore not a required item. Signature Scott M Queen Date 1/2005 1.1.8 Test case “8802 Reset Table View Column” 1.1.8.1 Test Description Have an option to reset the view of a table if a user changes it. 1.1.8.2 Procedure Prerequisites • Login to MainSaver Testing DB
  • 9. Mainsaver 8.300 Upgrade Functional Testing Documentation Actions • Navigate to maintenance module • Execute actions • Select “Work Order” button • Select “Define Query” button • When query box comes up select “All Records” check box • Select “options” in the top toolbar • Select “Reset Table View Column” Expected results: • Restored table view to previous settings Signature Scott M Queen Date 11/2004 1.1.9 Test case “4621 Mass Close Purchase Orders” 1.1.9.1 Test Description Add option of mass close purchase orders. 1.1.9.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to Purchasing module • Execute actions • Click on “Purchase Order” • Click on “Retrieve Query” • Select the date range you wish to go back to. • Once search results come back go to “File” • Select “Mass-Close Po” Expected results: • Closed out all Po’s that where in table view. Signature Scott M Queen Date 1/2005
  • 10. Mainsaver 8.300 Upgrade Functional Testing Documentation 1.1.10 Test case “5595 Using PDF’s With PM References” 1.1.10.1 Test Description The ability to now use PDF forms and attach them to a Pm reference tab. 1.1.10.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to Pm module • Execute actions • Click on Pm record you want to attach PDF forms. • Under the “References Tab” select “Add” • Input file name into references box. • Click OK • Next time the Pm is generated it will print the pdf. Expected results: • Can now Print out PDF forms. Signature Scott M Queen Date 1/2005
  • 11. Mainsaver 8.300 Upgrade Functional Testing Documentation 1.1.11 Test case “5953 Add Pm Id Number to Preventive Maintenance Work Order” 1.1.11.1 Test Description Add the Pm Id number to the Preventive Maintenance work order when it is generated. 1.1.11.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • No action needed. It automatically prints on the preventive maintenance work order. Expected results: • Pm Id is reflected on the preventive maintenance work orders. Signature Scott M Queen Date 11/2004 1.1.12 Test case “939 print A Work Order From Web Request Module” 1.1.12.1 Test Description To be able to print a work order once it has been changed from a request into a work order at the request screen. 1.1.12.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Click on Maintenance module • Click on the “Work Req” button • Click on “Retrieve Query” button • From the drop down arrow select “Pending Request” • Double click on a request • Enter the asset number that the request will be assigned to • Click OK • Once you are back to the “Pending Request” Screen select the request you just changed. • Click “Review” button on the toolbar
  • 12. Mainsaver 8.300 Upgrade Functional Testing Documentation • Click the “Approve” Button that appears on the bottom right hand corner. • The A status box will appear select the status code “Do” ready to be done like in previous version • Once that is selected check the check box below the status field that says “Print Work Order” This is the new feature that allows you to by-pass going to the work order module to print the work order. Expected results: • Printed the assigned work order from web request. 1.1.13 Test case “9099 Add Option Fields to Work Request Module” 1.1.13.1 Test Description Add the option fields that exist in the work order module to the request module so approvers can enter miscellaneous information via the request module. Prerequisites • Login to MainSaver Testing DB Actions • Navigate to Maintenance Module • Click on the “Work Req” button. • Go to “New” • You will see the (5) option fields and (2) date fields like the ones that exist in the work order module. Expected results: • The fields do exist in the work request new screen. Signature Scott M Queen Date 12/2004
  • 13. Mainsaver 8.300 Upgrade Functional Testing Documentation 1.1.14 Test case “9302 Changing Password Using Special Characters” 1.1.14.1 Test Description To be able to use special characters in a user password. 1.1.14.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to “System Administration Module” • Select a user name • Manually change the password and include special characters. Signature Scott M Queen Date 1/2005
  • 14. Mainsaver 8.300 Upgrade Functional Testing Documentation 1.1.15 Test case “9634 Can Not Automatically Enter In A Asset Number On The Fly” 1.1.15.1 Test Description Can not automatically add an asset “on the fly” via the Pm module 1.1.15.2 Procedure Prerequisites • Login to MainSaver Testing DB Actions • Navigate to “Preventive Maintenance Module • Execute actions • Click on “Pm” button • Select “New” button • When you type in an asset that does not exist in database it will prompt you if you want to add it. Signature Scott M Queen Date 1/2005 One SOP did change with this upgrade. A manual was made explaining the new option available in the work request section. Reference “939 Print A work Order from Web request” This was sent out on 01/24/2005 and all so made available on a group shared folder for Mainsaver.