Writing Tests

Tests are written using the sus testing framework.

Here’s an example of a test that verifies that a Traffic Light Controller responds with a NotAcknowledged if it receives a non-existing status request:

describe "Traffic Light Controller" do
  include RSMP::Validator::Helpers::Status

  it 'responds with NotAck to invalid status request code' do
    with_site(:connected) do |site_proxy|
      # write to the validator log
      log "Requesting non-existing status S0000"

      # expect an error to be raised
      expect {
        # request a non-existing status
        status_list = convert_status_list( S0000:[:status] )
        site_proxy.request_status RSMP::Validator.get_config('main_component'), status_list, collect: {
          timeout: RSMP::Validator.get_config('timeouts','command_response')
        },
        # normally we can't send S0000 because JSON Schema validation
        # will prevent it, but we can disable it for testing purposes
        validate: false
      }.to raise_exception(RSMP::MessageRejected)
    end
  end
end

The with_site helper handles the connection to the site, and will pass a site_proxy argument (RSMP::SiteProxy) which can be used to communicate with the site.

For example, you can request statuses, subscribe to statuses and send commands. Many of the methods allow you to wait for responses.

See the rsmp gem for more documentation.

Working with Exceptions and Timeouts

Timeouts are essential when testing external systems. When you send a command or request, you expect a response within a certain amount of time. These timeouts must be defined in the test configuration.

The rsmp gem will raise exceptions if a timeout is reached. Normally, you will not need to do any specific exception handling in your test code. Your test will be aborted and sus will catch the error and report the test as failed.

with_site helper

Writing Tests

Working with Exceptions and Timeouts

Table of contents