Aggregated Status

Tests

• Aggregated Status can be requested
• Aggregated Status uses null for functional position/state

Aggregated Status can be requested

Verify that the controller responds to an aggregated status request.

1. Given the site is connected
2. When we request aggregated status
3. Then we should receive an aggregated status

View Source

it 'can be requested' do
  with_site(:connected, core: '>=3.1.5') do |site_proxy|
    log 'Request aggregated status'
    site_proxy.request_aggregated_status_and_collect(
      RSMP::Validator.get_config('main_component'),
      within: RSMP::Validator.get_config('timeouts', 'status_response')
    ).ok!
  end
end

Aggregated Status uses null for functional position/state

Verify that aggregated status uses null for unused attributes, from SXL 1.1 For SXL versions before 1.1 empty strings “” is also allowed.

1. Given the is reconnected
2. When we receive an aggregated status
3. Then fP and fS should be null

View Source

it 'uses null for functional position/state' do
  with_site(:isolated, sxl: '>=1.1',
                       'collect' => {
                         filter: RSMP::Filter.new(type: 'AggregatedStatus'),
                         timeout: RSMP::Validator.get_config('timeouts', 'ready'),
                         num: 1,
                         ingoing: true
                       }) do |site_proxy|
    collector = site_proxy.collector
    collector.use_task Async::Task.current
    collector.wait!
    aggregated_status = site_proxy.collector.messages.first
    expect(aggregated_status).to be_a(RSMP::AggregatedStatus)
    expect(aggregated_status.attribute('fP')).to be_nil
    expect(aggregated_status.attribute('fS')).to be_nil
  end
end