Skip to content

Functional Tests for ERS Messages

EDIT: This issue will be solve the lack of a functional test for ERS messages.

---------- OLD Description --------------

This can be approached in multiple ways:

  • A We unittest our own implementation, that is, only OUR code.

    • Pros: When test fails, we can be sure it is our fault, and we are the ones to fix it.
    • Cons: Test can't tell if the ERS service is running, or if we are using the ERS lib properly

  • B We test ERS functionality (that is, we test the library)

    • Pros: Ensures our understanding of the library, and that it is working as we expect.
    • Cons: We're testing someone else's library.

  • C We test the integration with the service, that is, we check that our implimentation and the ERS service is working together

    • Pros: Good for ensuring compatibility with ERS and that "everything" works.
    • Cons: Might fail even if it's not our fault, (ERS service is down, missing libraries)

Suggestion:

Edited by Jonas Ladefoged Holm