TEST CASES DOCUMENTATION - davisyo/SEATcode GitHub Wiki

In this section the 4 designed test cases are documented using the IEEE289 Standard:

• Identifier: test_case1_boundaries

• Description: In this test case two rovers will try to move beyond the boundaries of the plateau, both horizontally and vertically

• Input specifications:

  9 4
  2 3 E
  M M R M M L L M
  5 0 S
  M M L M M M L M M M R M M M

• Ouput specifications:

  • Expected output:

    4 2 N
    9 3 E

  • Messages: none

• Identifier: test_case2_emptyfile

• Description: In this test case the app will be run with an empty input file

• Input specifications:

  <empty_file>

• Ouput specifications:

  • Expected output: Error
  • Messages:

    "The input file is empty"

• Identifier: test_case3_wronginstructions

• Description: In this test case several non defined characters and blank spaces will be scatter among the movement strings of the rovers. The app should be able to report the invalid characters to the user and then ignore them and the blank spaces according to the design specifications.

• Input specifications:

  5 5
  1 2 N
  L M X L M L 66 M L M M
  3 3 E
  M M R M M R M R R QQQT M

• Ouput specifications:

  • Expected output:

    1 3 N
    5 1 E

  • Messages:

    Detected not valid instruction: X at position: 3
    Detected not valid instruction: 6 at position: 7
    Detected not valid instruction: 6 at position: 8
    Detected not valid instruction: Q at position: 10
    Detected not valid instruction: Q at position: 11
    Detected not valid instruction: Q at position: 12
    Detected not valid instruction: T at position: 13

• Identifier: test_case4_wronglength

• Description: In this test case the movement string for the second rover is missing. The app should report it and stop the program according to the specifications

• Input specifications:

  5 5
  1 2 N
  L M L M L M L M M
  3 3 E

• Ouput specifications:

  • Expected output: Error
  • Messages:

    No movement string defined for rover 2