Skip to content

manualtestcalendar.md

Latest commit

 

History

History
146 lines (99 loc) · 5 KB

manualtestcalendar.md

File metadata and controls

146 lines (99 loc) · 5 KB

In this demo you will

  • Start locally HAM server
  • Start the sample application
  • Connect to it through proxy
  • Record the interactions of the sample application
  • Setup a null-infrastructure test. Testing manually with
    • Simulated Back-end
    • Simulated Back-end to Back-end interaction

For more infos check here

Download the last release

Download the two tar.gz, ham and ham-samples from github releases and extract them in the same directory

Starting the sample application

Go on the "calendar" directory and run "runcalendar.bat/sh"

This will start

The calendar sample project

It's composed of three parts

  • FE, that calls gateway for all its needs
  • GATEWAY, that acts a "middleman" between FE and BE
  • BE, with the database that is called only by the GATEWAY

Configure proxy

Should set the proxy to 127.0.0.1 And port 1080 for socks5 or 1081 for http/https

Click me for more explanations

  • Chrome:

    • Install Proxy Switch Omega
    • Go to options
    • Add http and https proxy server with

      • Address: 127.0.0.1

      • Port 1081.

        Ham Proxyes
    • Select "proxy" from the extension menu and back to "direct" when you want to disconnect
    • Ham Proxyes

  • Firefox

    • Navigate to about:preferences

    • Search for "proxy"

    • Click on "Settings"

    • Go to "Manual proxy Configuration"

    • Select the socks5 proxy

      • Address: 127.0.0.1
      • Port 1080

    • Check the "Proxy DNS when using SOCKS v5" flag

    • Clean the settings when needed

      Ham Proxyes

Record some interaction

You can now check ham application going on http://www.local.test

  • Going on ham proxyes you can verify that all proxies are ok if they don't work just "Refresh Status"

Ham Proxyes

  • Navigation on the application you can try some interaction

Sample application

Create recording

  • Once you create the recording you can start recording!

Start recording

  • Go then on the application and do some interaction
    • Add an Employee "John Doe"
    • Go on Appointements
    • Add an Appointment with "Doctor" as description
    • Change the state of the appointament till it shows "Confirmed"
    • Delete the appointment
    • Back on employee, delete the employee too
  • And stop the recording!
  • Now you will se all the calls on the just created recording

Start recording

  • "Download" the recording as "Sample.json"

Simulate the calendar back-end

Test the interaction between front and mock gateway

  • Stop the application and restart!
  • Delete the script and re-upload Sample.json
  • Select all the calls to www.sample.test with the filter and delete them all

  • Select all the calls to path /int/be.sample.test with the filter and delete them all

  • Stop the "be" application
  • Stop the "gateway" application
  • Download and save the script as NullGateway.json
  • Play the Script with "Play"
  • Do the navigation as you did while recording
  • Everything will work as if be is up!

Test the interaction between fe-gateway and mock be

  • Stop all the applications and restart!
  • Delete the script and re-upload Sample.json
  • Select all the calls to www.sample.test with the filter and delete them all

  • Select all the calls to path /int/gateway.sample.test with the filter and delete them all

  • Stop the "be" application
  • Download and save the script as NullBe.json
  • Play the Script clicking on "Play"
  • Do the navigation as you did while recording
  • Everything will work as if gateway is up!