-
Notifications
You must be signed in to change notification settings - Fork 17
PreFlight Testing
- Manual Testing
There are many tests in our integration suite that are tagged manual and do not run on integration testing. We should cover all these cases.
Currenly I think these are just some Mode Manager Tests.
- Startup Testing
In nominal conditions, does the satellite startup from being deployed, wait 45 minutes, run all its startup commands and beacon. Can a listening ground station listen to it and command it? Check boot count and mode_state files
We also want to test the satellite starting up in a number of configurations:
- Starting up in normal mode
- Starting up in safe mode
- Starting up when command loss time set off
- Starting up in detumble
- Starting up with no startup sequence
- Day of the life testing
Using the Radio as an operator, uplink the sequences and run the day in the life tests (test_day_in_the_life.py). These include
- Changing the radio settings with radio_fast.seq
- Running payload operations using
- Running the edge cases in day of the life
- Downlinking files (ex Photos, Telemetry on Boot)
- Over the Air update Testing
- Do an over the air update over the radio. Test that you can revert back to the golden parition on command loss, commanded reset and/or fault from the test parition.
- Payload Testing Because these satellites have specific non-camera payloads, Run the payload in nominal and off nominal conditions. This includes getting data down.
- Nominal acquire + store + Downlink
- Power off / on cycling on operation
- Command while safe mode
- Payload fault, check if goes into safe mode when it can
- What happens on a broken filesytem or RTC
- Stress Testing
This is a big one, we only realized we had RAM issues last time because we ran stress testing and observed abnormal behavior. Have everything be on for a longer period of time, and stress the system
- All load switches on + detumble AUTO + LoRa TX + high telemetry rate, Three sequencers concurrent
- Rapid command uplink (auth + bypass)
- Telemetry Testing
Check we get all the telemetry we need as we toggle the different levels of telemetry.
Run startup with nothing in pre_deployment.tlm, then downlink it when its done
Edge Cases
- Filesystem Stressing: Power loss while writing, Continous file creation writing
- RTC: Time Set Command, Time Set being removed. What happens to Detumble/sequences/any compnent that depends on time
Test satellite jamming with two spacecraft and run the startup