Skip to content

Latest commit

 

History

History
47 lines (35 loc) · 4.04 KB

testing-plan.md

File metadata and controls

47 lines (35 loc) · 4.04 KB
Raw

Testing Plan

This doc lays out a basic testing plan for verifying myceli functionality in a lab, dev, or live setup.

This doc will not cover any hardware or system specifics around running myceli. This includes radio configuration, how/where to run myceli, or even how to configure myceli. All of these specifics are assumed to be system dependent and will change based on the hardware and it's deployment configuration.

This doc will cover generic behavioral testing plans for myceli which can be used to validate any myceli installation or configuration.

Test Case - Verify Myceli Instances Alive

Steps:

  1. Using controller software, send the RequestAvailableBlocks command to the myceli ground instance.
    • This step passes if an AvailableBlocks response is received. Any other response / no response is a failure.
  2. Using controller software, send the RequestAvailableBlocks command to the myceli space instance.
    • This step passes if an AvailableBlocks response is received. Any other response / no response is a failure.

This test case passes if both steps pass.

Test Case - Retrieve an IPFS File

Steps:

  1. Using the controller software, send the ImportFile command to the myceli space instance with a known good path for the one-pass payload file.
    • This step passes if an FileImported response with CID is received. Any other response / no response is a failure.
  2. Using the controller software, send the TransmitDag command to the myceli space instance with the CID obtained from the FileImported response and with the network address of the space-to-ground radio link.
  3. Using the controller software, send the ValidateDag command to the myceli ground instance with the CID obtained from the FileImported response.
    • This step passes if an ValidateDagResponse response with true. Any other response / no response is a failure.
  4. Using the controller software, send the ExportDag command to the myceli ground instance with the CID obtained from the FileImported response and a writeable file path.
    • This step passes if myceli is able to correctly write a file to the given file path.

This test case passes if the final step is successful and the resulting written file matches the onboard payload file.

Test Case - Send and Retrieve New IPFS File

Steps:

  1. Using the controller software, send the ImportFile command to the myceli ground instance with a known good path for the one-pass payload file.
    • This step passes if an FileImported response with CID is received. Any other response / no response is a failure.
  2. Using the controller software, send the TransmitDag command to the myceli ground instance with the CID obtained from the FileImported response and with the network address of the ground-to-space radio link.
  3. Using the controller software, send the ValidateDag command to the myceli space instance with the CID obtained from the FileImported response.
    • This step passes if an ValidateDagResponse response with true. Any other response / no response is a failure.
  4. Shutdown the myceli ground instance, delete the storage database, and start the myceli ground instance again.
  5. Using the controller software, send the TransmitDag command to the myceli space instance with the CID obtained from the FileImported response and with the network address of the space-to-ground radio link.
  6. Using the controller software, send the ValidateDag command to the myceli ground instance with the CID obtained from the FileImported response.
    • This step passes if an ValidateDagResponse response with true. Any other response / no response is a failure.
  7. Using the controller software, send the ExportDag command to the myceli ground instance with the CID obtained from the FileImported response and a writeable file path.
    • This step passes if myceli is able to correctly write a file to the given file path.

This test case passes if the final step is successful and the resulting written file matches the originally transmitted payload file.