The following exercises demonstrate how to use SOAtest to perform functional testing on the Web interface. It covers:


Web interface testing is difficult to automate. Teams often abandon automated testing in favor of manual testing  due to too many false positives or too much effort required to maintain the test suites.

SOAtest facilitates the creation of automated test suites that are reliable and dependable. Its ability to isolate testing to specific elements of the Web interface eliminates noise and provides accurate results.

SOAtest isolates and tests individual application components for correct functionality across multiple browsers without requiring scripts. Dynamic data can be stubbed out with constant data to reduce test case noise. Validations can be performed at the page object level as well as the HTTP message level. SOAtest also verifies the client-side JavaScript engine under expected and unexpected conditions through asynchronous HTTP message stubbing.

Cross-browser Testing and Validation Video Overview

Recording in a Browser

Before performing the following exercises, ensure that you have started the ParaBank Server (as described in Setting Up ParaBank) and that you can navigate successfully to the default address (localhost:8080/parabank). Close the browser window after you verify this.

To record in a browser:

  1. Right-click the project from the previous exercises, then choose Add New> Test (.tst) File from the shortcut menu.

  2. Enter a name for the file, then click Next.
  3. Select Web> Record web scenario and click Next.

  4. In the first Record Web Scenario wizard page, ensure that Record new web scenario is selected, then click Next.

  5. Complete the next  Record Web Scenario wizard page as follows:
    1. Enter Web Functional Testing  in the Test Suite Name field.
    2. Enter localhost:8080/parabank in the Start Recording From field.

      Internet Explorer Note

      If you will be using Internet Explorer to record/playback this test, use the name of the local machine instead of localhost—here and throughout this tutorial lesson.
    3. Ensure that the following options are checked, and the others are not:
      • Generate Functional Test
      • Generate Asynchronous Request Tests.

    4. Click the Finish button. The test will begin, and a browser window will open.
  6. Within the browser window that opens, perform the following actions:
    1. Type john in the Username field.
    2. Type demo in the Password field.
    3. Click Log In.

    4. Click the first account number listed in the Accounts Overview page (12345).

    5. Click Log Out.

    6. Close the browser to end recording. In the Test Case Explorer view, SOAtest creates a new .tst file and a test suite that contains the scenario that you just recorded.
  7. Expand the new test suite node in the Test Case Explorer to view the tests created for each user action taken during the recording.

Adding a Data Source

To add a data source:

  1. Right-click the Scenario: Web Functional Testing node, then choose Add New> Data Source from the shortcut menu.

  2. In the New Project Data Source wizard, select Table and click Finish.

    A new Data Sources node is added to the Scenario: Web Functional Testing branch.
  3. In the New Datasource table configuration panel that is opened in the right side of the GUI, make sure the First row specifies column names check box is checked.
  4. Enter Account Number in the top cell in column A. In the same column, enter 12345 in row 1 and 13344 in row 2.

  5. Click Save to save the changes.

Parameterizing a Form Input

To parameterize an action:

  1. Expand the Scenario: Web Functional Testing branch to view the recorded actions related to clicking the account number.
  2. Double-click the Test 3: Click “12345" node to open the test configuration panel.
  3. Note that the Pre-Action Browser Contents tab shows what the page looked like before the test action (clicking ‘12345’) was performed. It uses a blue border to highlight the user actionfor this test.

  4. In the test configuration panel, open the User Action tab.
  5. Under the Element Locator section, change Attribute value from Fixed to Parameterized.
  6. Select Account Number from the menu that appears to the immediate right.

  7. Click Save to save the changes.
  8. Run the test. It will now click on the <a> element that has been parameterized with the account number entered in the data source.

Configuring Validation on a Page Element

To configure a validation on a page element:

  1. Fully expand the Scenario: Web Functional Testing branch.
  2. Double-click the Browser Contents Viewer node under Scenario: Form login> Test 3: Click ‘Log In’.

  3. In the Browser Contents Viewer configuration panel, right-click the dollar amount text that appears next to account 12345 (-$2300.00) and select Extract Value from <TD> element from the shortcut menu.

  4. In the dialog that opens, ensure that the text property is selected in the Property name box, then click Next.

  5. Complete the next page as follows:
    1. Check Isolate partial value using text boundaries box.
    2. In the Left-hand text field, enter -$. You will see that the ‘Preview of Value to Validate…’ text now contains only the dollar amount. The Left-hand text that you added removes the dollar sign from the validation, allowing you to focus on validating the actual amount.

    3. Click Next.
  6. Ensure that Validate the value is selected, and that the expected text is displayed on the rendered page.

  7. Click Finish. A  Browser Validation Tool will be added to this test. As the red highlight indicates, it is set up to check that the element you selected remains the same as the application evolves.

Configuring a Browser Stub

A stub is static data that SOAtest saves when recording a web scenario. Stubbing helps to verify that any changes to the client-side code do not affect the final resultant html page by feeding unchanging data to the client in place of the actual server response.

To configure a browser stub:

  1. Expand the Scenario: Web Functional Testing branch.
  2. Right-click Scenario: Form login> Test 3: Click ‘Log In’ and choose Add Output from the shortcut menu.

  3. In the Add Output wizard that opens, choose HTTP Traffic, then click Next.

  4. Select http://localhost:8080/parabank/overview.htm and click Next.

  5. In the left panel, select Both> Stub Request/Response.
  6. In the right panel, select any Browser Stub.
  7. Click Finish.

  8. In the Response Body section of the Browser Stub configuration view (opened on the right side of the GUI), change the dollar amount in the table from its existing value of -$2300 to $1000.00.
    • The easiest way to do this is to copy the entire text in the Response Body into a text editor (e.g. Notepad), use its search capability to find the previous dollar amount, modify the value, and then copy all the text from the editor and replace the current contents in the Response Body.
    • This response body will be provided in place of the actual server response when the recorded scenario is run later in this example.

  9. Click Save to save the changes.

Playing a Recorded Scenario in a Browser

To playback the recorded scenario in a browser:

  1. In the Test Case Explorer, select the Scenario: Web Functional Testing node.
  2. Click the Test toolbar button.

The recorded scenario will now be played back in your browser, once for each search value that we parameterized in a previous section of this example. Please wait for each action to be played out in your browser.

Note if you have been following the complete tutorial, errors will be reported due to the Browser Stub tool that was previously added. This is expected.

Performing Static Analysis During Web Scenario Execution

To configure SOAtest to perform static analysis on the Web pages that the browser downloads as web scenarios execute:

  1. In the Test Case Explorer, select the Scenario: Web Functional Testing node.
  2. Open the Test toolbar button’s pull-down menu, then choose one of the available static analysis configurations.

When SOAtest is finished performing static analysis, static analysis violations are shown in the Quality Tasks view. To facilitate review of these results:

  1. Open the pull-down menu on the top right of the Quality Tasks view.

  2. Choose Show> SOAtest Static Analysis for Functional Tests Layout.
  • No labels