Functional testing. Appendix: Sample test plan

Transcription

1 Tool WinRunner is a powerful automated functional testing tool developed by Mercury Interactive. It allows a user to record and play back user interface actions as test scripts. Pre-Requisites WinRunner 7.0 needs to be installed on the system in standalone mode. Test Scripts, GUI Maps, and spreadsheets to facilitate data-driven tests must be available in folders in a specified directory structure. Specific GUI Maps have to be loaded in WinRunner before running scripts. Approach An automated smoke test suite will be developed for ACE. This will concentrate on the User Interface and functional aspects of the application. Default window functionality (i.e. Minimize, Maximize, Move, Size, System Menu Options) will be part of the automated suite by default. The User Interface will be verified against a base-lined version of the screens and forms. The forms and windows will be base-lined by the end of the testing phase, once all issues and defects for the application have been resolved. The following items will be checked for each form / window as default: 1. All possible navigation paths to the form / window 2. Presence of all controls within the form / window 3. Alignment of all controls 4. Default state of each control (enabled / disabled) 5. Text labels and fonts The above features will be verified by the automated suite in addition to the specific test cases that will be designed as part of manually testing the product. The testing of ACE can be divided into the following categories: 1. User interface 2. Wizards 3. Commands 4. Report writer 5. Word correspondence Sample test plan 1

2 6. Dialog Designer 7. ScriptNet Utility and Miscellaneous Checking User Interface Using menu 1. Use the File menu to open Select a Connection window (Open). 2. Select an existing connection and click the connect button. 3. Mention a valid User ID and Password Use in the Sign on screen. 4. Use the Edit menu to perform the following actions: a. To Cut/Copy/Paste/Insert/Delete b. To check spelling (Spell Check) c. To open the Scratch Pad window (Scratch Pad) d. To add a text into the Scratch Pad (Add to Scratch Pad) 5. Use the View menu to perform the following actions: a. To change the size of your session window (Reduce/Enlarge/Restore). b. To make single or multiple snapshot of a screen in the active session. c. To clear (erase) all snapshot windows (Clear Snaps). 6. Use the Preferences menu to perform the following actions: a. To change Settings (Settings) b. To change Keyboard Layout (Keyboard) 7. Use the Tools menu to perform the following actions: a. To get the Logging Window (Logging). b. To get the Timing Window (Timing) c. To get the Mouse Coordinate (Show Mouse Coordinate) d. To get the Open Cache window (Caching) e. To get the Workflow Architect s Assistant f. To reset the communication (Reset Communication) 8. Open another window and Use the Window menu to perform the following actions: Sample test plan 2

3 a. Tile/Cascade/Arrange Icons b. Switching Between Windows 9. Use the Help menu to perform the following actions: a. To view help on PegaVIEW ACE b. To view help on Resource c. To Explain d. To get the Copyright message. 10. Use the File menu to perform the following actions: a. To Print (Print All/Print Session/Print Setup) b. To Close the current session c. To shut down ACE and all of your open sessions Using Toolbar 1. Use the File menu to open Select a Connection window (Open). 2. Select an existing connection and click the connect button. 3. Mention a valid User ID and Password Use in the Sign on screen. 4. Perform the following actions from the Toolbar: a. Click the Cut/Copy/Paste button. b. Click the Scratch Pad window button. c. Click Add to Scratch Pad button. d. Go to one IENT screen and click the Approve Button. e. Click the Back button. f. Click the NEXT button. g. Click the Go to Command Screen button. h. Click Stack Current Screen button. i. Click Electronic Message Work List button. j. Click Electronic message display button. k. Click Electronic Mail enter button. l. Click Electronic Message Cancel button. Sample test plan 3

4 m. Click Electronic mail update button. n. Click Work Item Work list button. o. Click Work Item Work Display button. p. Click Work Item Audit Display button. q. Click Work Item Change button. r. Click Work Item Find button. s. Click Work Item Transfer button. t. Click Print Logical Screen Button. u. Click Display Help Field Button. Checking wizards 1. Use the File menu to open Select a Connection window (Open). 2. Select an existing connection and click the connect button. 3. Mention a valid User ID and Password Use in the Sign on screen. 4. Type the Command and the associated parameter to launch the wizard. 5. Navigate all the screens from the Main window. 6. Check the expected results. Checking ACE commands 1. Enter the Command with the required parameters. 2. Check that the Command executes properly. 3. Enter the data in the fields if required. 4. Click Approve if required. 5. Check that the Command approves properly. Checking Report Writer 1. Enter the Command with the required parameters. 2. Check that the Command executes properly. 3. Enter the data in the fields if required. 4. Click Approve. Sample test plan 4

5 5. Check that the Command approves properly. Checking Word Correspondence 1. Enter the Command with the required parameters. 2. Check that the Command executes properly. 3. Enter the data in the fields if required. 4. Click Approve. 5. Check that the Command approves properly. Checking Dialog Designer The testing of Dialog Designer can be divided into the following categories: 1. Checking of the existing forms a. Open an existing form, which will be used as a template for testing. b. Edit all the objects present in the form. c. Check the object info for regression testing. d. Move/Size all types of the objects present in the form. e. See the form in Test mode. 2. Editing/modifying the existing forms a. Open an existing form, which will be used as a template for testing. b. Edit all the objects present in the form. c. Change the object info and test whether that is implemented or not. d. Adding new form e. Add a new form. f. Add all type of the objects in the form. g. Edit the object info and test whether that is implemented or not. h. See the form in Test mode. Checking miscellaneous features Setup Net utility is considered in Miscellaneous Features, which can be divided into the following categories: Sample test plan 5

6 1. Adding new Connection Profile a. Select File New from menu. b. Add one or more partner with available transports (Mention Name, Description, Host Name and Port Number). c. Delete any partner if required. d. Save the Connection Profile as Connect.ini file. e. Close the Connection Profile. 2. Editing/modifying the existing forms a. Select File Open from menu. b. Select the Connect.ini file to modify. c. Add one or more partner with available transports (Mention Name, Description, Host Name and Port Number). d. Edit an existing partner to modify its properties (Name, Description, Host Name and Port Number). e. Copy a partner and name it with a different name. f. Delete any partner if required. g. Save the Connection Profile as Connect.ini file. h. Close the Connection Profile. Sample test plan 6