Option

Option

  • Option column is used to overwrite configuration values for Interfaces

  • The override is only for the test the option is invoked on

  • Format: key value pair

    • Syntax: in csv option column: key:value. eg. WAIT_FOR_RESPONSE:5

    • Multiple values are separated by ";"

Global

  • Global options apply to all Interfaces

  • RUN_COUNT: how many times to run the current tests case

    • eg. creating multiple orders

    • eg. RUN_COUNT:3;

  • DEPENDS_ON_TEST: specify which previous test the current test depends on

    • If dependent test fail, the current test will be skipped

    • Syntax:

      • DEPENDS_ON_TEST:testCaseId

    • eg. DEPENDS_ON_TEST:testId1;

RestfulApi Interface

Retry Options

  • NO_VALIDATION_TIMEOUT: disabled timeout validation. Sets property service.timeout.validation.isEnabled to false

    • There is no value associated with this

    • Timeout validation means waiting in seconds for expected response. Expected response values can be in both expected RespCodeExp and ExpectedResponse columns.

  • WAIT_FOR_RESPONSE: enables timeout validation.Sets value in seconds.

    • Timeout validation means waiting in seconds for expected response. Expected response values can be in both expected RespCodeExp and ExpectedResponse columns.

    • eg. WAIT_FOR_RESPONSE:5

  • WAIT_FOR_RESPONSE_DELAY_SECONDS: wait time between each timeout validation response in seconds

    • Overwrites properties value: service.timeout.validation.delay.between.attempt.seconds

    • Timeout validation means waiting in seconds for expected response. Expected response values can be in both expected RespCodeExp and ExpectedResponse columns.

  • RETRY_COUNT: Set retry count if validation at RespCodeExp or ExpectedResponse column is not met.

    • This is different from Timeout Validation as that is based on time, this is based on count

    • Overwrites property value: service.retry.count

    • eg. RETRY_COUNT:3

  • RETRY_AFTER_SECONDS: Seconds to wait between each test retry.

    • Set with RETRY_COUNT

    • Overwrites property value: service.retry.after.seconds

    • eg. RETRY_AFTER_SECONDS:3

Pagination Testing

  • Pagination testing, refers to rest api calls with response separated in pages; hence, we need to navigate through the pages to find the desired result

  • PAGINATION_STOP_CRITERIA: Json path criteria to stop searching

    • The Json path would refer to an item on the page that we expect to be available on each page that has content. Once the result returns empty, then we stop searching

    • eg. PAGINATION_STOP_CRITERIA: .id

      • if no id's are returned, we stop

  • PAGINATION_MAX_PAGES: Maximum number of pages to navigate before stopping

    • eg. PAGINATION_MAX_PAGES:10

  • PAGINATION_FROM: Starting page to starting searching for results

    • eg. PAGINATION_FROM:1

  • PAGINATION_INCREMENT: How many pages are incremented each time

    • eg. PAGINATION_INCREMENT:1

Database Interface

  • database: specify the database number to use

    • database sets in config file

    • eg. database:2

      • selects database set 2 to use in the current test

    • # Database Server
db.1.driver = org.postgresql.Driver
db.1.url=jdbc:postgresql://localhost:5432
db.1.name=testdb
db.1.username=postgres
db.1.password=123

db.2.driver = org.postgresql.Driver
db.2.url=jdbc:postgresql://localhost:5432
db.2.name=testdb2
db.2.username=postgres
db.2.password=123

Retry Options

  • NO_VALIDATION_TIMEOUT: disabled timeout validation. Sets property service.timeout.validation.isEnabled to false

    • There is no value associated with this

    • Timeout validation means waiting in seconds for expected response. Expected response values can be in both expected RespCodeExp and ExpectedResponse columns.

  • WAIT_FOR_RESPONSE: enables timeout validation.Sets value in seconds.

    • Timeout validation means waiting in seconds for expected response. Expected response values can be in both expected RespCodeExp and ExpectedResponse columns.

    • eg. WAIT_FOR_RESPONSE:5

  • WAIT_FOR_RESPONSE_DELAY_SECONDS: wait time between each timeout validation response in seconds

    • Overwrites properties value: service.timeout.validation.delay.between.attempt.seconds

    • Timeout validation means waiting in seconds for expected response. Expected response values can be in both expected RespCodeExp and ExpectedResponse columns

Rabbit MQ

  • exchange: exchange to send messages

    • eg. exchange:exchange1

  • queue: queue to send messages

    • eg. queue:queue1

  • outbound_exchange: exchange to receive messages

    • eg. outbound_exchange:outboundExchange1

  • outbound_queue: queue to receive messages

    • eg. outbound_queue:outboundqueue1

  • response_identifier: unique identifier for message received

    • This is the means we associate the receiving messages with the current test

    • eg. response_identifier:order5434

  • WAIT_FOR_RESPONSE: how long in seconds we wait for the desired message to appear

    • eg. WAIT_FOR_RESPONSE:60

KAFKA

  • topic: kafka topic to receive messages

  • response_identifier: unique identifier for message received

    • This is the means we associate the receiving messages with the current test

    • eg. response_identifier:order5434

  • WAIT_FOR_RESPONSE: how long in seconds we wait for the desired message to appear

    • eg. WAIT_FOR_RESPONSE:60

SERVICE BUS

  • topic: topic to send message

  • outbound_topic: topic to receive message

  • host: host to connect to

  • response_identifier: unique identifier for message received

    • This is the means we associate the receiving messages with the current test

    • eg. response_identifier:order5434

  • WAIT_FOR_RESPONSE: how long in seconds we wait for the desired message to appear

    • eg. WAIT_FOR_RESPONSE:60

PreviousRequestBodyNextOutputParam

Last updated

Was this helpful?