Monitor Test Specification

Author: Libor Martinek, Martin Schovanek
Version: 1.1.3
Last update: 04.02.2005
Introduction: The HTTP Monitor collects data about HTTP requests and allows the user to view that data through a GUI component of the IDE. The Monitor is intended to be a tool for helping debug web applications by allowing a JSP/Servlet developer to view specific information about a request and to save and replay transactions. In Netbeans 4.1 is possible to deploy web application on Sun Java System Application Server 8.1,which don't support the monitor by default.You must change it in Appserver properties before deploying application.
Test on both Tomcat and Application server.

Comment: Updated by Jaroslav Pospisil

Table of Contents

Test suite 1: Opening HTTP Monitor

Purpose: To verify thaty monitor is properly opened at all conditions.
Setup: Have mounted a webmodule and HTTP Monitor closed.

#Test caseDescription
1Open HTTP Monitor by main window menu
1. In the main window, select the Window menu.
2. Select HTTP Monitor from the Window menu.
RESULT: HTTP Monitor should be displayed.
2Open HTTP Monitor by mnemonic
1. With the main window active, use 'Alt-W' to open the Window menu.
2. Use the 'H' mnemonic to select HTTP Monitor.
RESULT: HTTP Monitor should be displayed.
3Open HTTP Monitor by shortcut
1. Press Ctrl + 7.
RESULT: HTTP Monitor should be displayed.
4Open HTTP Monitor from toolbar
1. Right click the main toolbar line and choose 'Debug'.
2. Click the HTTP Monitor button on toolbar.
RESULT: HTTP Monitor should be displayed.
5Open HTTP Monitor by debugging a JSP
1. Open a JSP in the source editor.
2. Set some breakpoints in the JSP.
3. Start the debugger on the JSP by Run > Run Other > Run ".jsp" in Debugger.
RESULT: HTTP Monitor should be displayed.
6Open HTTP Monitor by debugging a Servlet
1. Open a servlet in the source editor.
2. Set some breakpoints in the servlet.
3. Start the debugger on the servlet by Run > Run Other > Run ".java" in Debugger.
RESULT: HTTP Monitor should be displayed.
Teardown:



Test suite 2: GUI Integrity

Purpose: Assuring all GUI parts are on proper place.
Setup: Open HTTP monitor with some current and also with some saved records.

#Test caseDescription
1Windows System
1. Move HTTP Monitor to other places/tabs.
RESULT: HTTP Monitor should be always correctly displayed.
2View data of a record
1. Click on a record.
2. Traverse all tabs and look at record's data.
RESULT: All record's data are correctly displayed.
3Sorting of records
1. Sort records by time asc./desc. and by alphabet.
RESULT: Records have to be ordered corectly.
4Sorting of query strings
1. Sort query strings by alphabet asc./desc. and unsort.
2. Move to other tab and back to check whether sorting preserves.
RESULT: Query strings have to be ordered corectly.
5Sorting of headers
1. Sort headers by alphabet asc./desc. and unsort.
2. Move to other tab and back to check whether sorting preserves.
RESULT: Headers have to be ordered corectly.
6Show timestamp
1. Show and hide timestamp of records.
RESULT: Timestamp have to be shown/hidden corectly.
Teardown:



Test suite 3: Work with records

Purpose: Save, delete and reply records.
Setup: Have webmodule with a JSP.

#Test caseDescription
1Save records
1. Save records.
RESULT: Record has to move from current to saved.
2Save multiple records
1. Save multiple selected records.
2. Try to save multiple selected records acroos current and saved folder.
RESULT: Record has to move from current to saved. Save multiple selected records across both folders shouldn't be allowed.
3Delete record
1. Delete record from current folder.
2. Delete record from save folder.
RESULT: Records have to properly deleted.
4Delete all record
1. Delete all record from current folder.
2. Delete all record from save folder.
3. Delete all record.
RESULT: Records have to properly deleted.
5Delete empty folders
1. Delete all record from current folder.
2. Delete all record from save folder.
3. Delete all record.
RESULT: No error should appear.
6Delete multiple selected records
1. Select multiple selected records from current folder.
2. Select multiple selected records from saved folder.
3. Select multiple selected records across current and saved folder.
4. Delete all record from save folder.
5. Delete all record.
RESULT: No error should appear.
7Reply record
1. Reply current record.
2. Reply saved record.
RESULT: The request represented by the record should be replayed. The request should be sent to the browser and a new record should be recorded by Monitor for the replay request.
8Reply record
1. Edit and Reply current record.
2. Edit and Reply saved record.
RESULT: The request represented by the record should be replayed. The request should be sent to the browser and a new record should be recorded by Monitor for the replay request.
9Session Cookie
1. Use Mozilla as external browser.
2. Open monitor and click on "Use the browser's session cookies for replay."
3. Execute createCookies.jsp.
4. Execute showCookies.jsp.
5. Open Cookies Manager in Mozilla and remove TestCookie1
6. Right-click on showCookies entry in monitor and select Replay. You should not see TestCookie1, just TestCookie2.
7. click on "Use recorded session cookies for replay.
8. Right-click on showCookies entry in monitor and select Replay. You should see both TestCookie1 and TestCookie2.
RESULT: Browser's session cookies and recorded session cookies should be used properly.
Teardown:



Test suite 5: Editing Records

Purpose: Assuring that Gui that make possible to edit record expose desired functionality.
Setup: Edit some record and change any parameters.

#Test caseDescription
1Display dialog to edit record.
1. Click on record
2. Using context menu choose Edit and Replay option
RESULT: The dialog should appear.
2Try to change and add some parameters.
1. Click on Add Parameter and add parameter
RESULT: Added parameters should exist in Query Window
3Choose tab Request
1. Change the f.e. method to POST or PUT
RESULT: Method should bi visible on request tab.
4Choose a cookie tab.
1. Introduce new cookie.
RESULT: Cookie should be visible on Cookie tab
5Choose Headers tab.
1. Change or add parameters of headers.
RESULT: Created headers should be visible.
Teardown:



Test suite 6: Internal HTTP Server

Purpose: Internal HTTP server is required for HTTP Monitor to proper work.
Setup: Internal HTTP server is running on port 8082, HTTP Monitor is open.

#Test caseDescription
1Change port of internal HTTP server
1. Stop the internal HTTP Server
2. Change the port number
3. Start internal HTTP Server
4.
RESULT: Http monitor does't intercept records.
2Execute with internal HTTP server stopped
1. Stop internal Http server
2. Make the request.
RESULT: Http monitor does't intercept records.
Teardown:



Test suite 7: Other functions

Purpose:
Setup:

#Test caseDescription
1Automatic Update
1. Open the HTTP Monitor window if it is not already opened.
2. Make requests for JSPs and servlets while the Monitor window is open.
RESULT: The Monitor window should automatically update with records for the new requests.
2Restart
1. Let HTTP Monitor open with several records in current and save folder with some orders defined.
2. Restart IDE
RESULT: HTTP Monitor should appear as was before restart with exception of current folder which should be exmpty.
3Help
1. Whenever you are in HTTP Monitor, press F1.
2. Right-click a Monitor record and choose "Edit and replay".
3. Click the Help button or press F1.
RESULT: Everytime you should get help "Monitoring Data Flow on the Web Server" or "Editing and Replaying Requests in the HTTP Monitor" if you are in Edit and Replay dialog.
Teardown:




Generated: Sat Jun 12 19:01:30 CEST 2004

Project Features

About this Project

QA was started in November 2009, is owned by Jiří Kovalský, and has 97 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20160708.bf2ac18). © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close