Automated testing #33

New Issue

logan · 2024-04-07T18:00:13-04:00

logan commented

2024-04-07 18:00:13 -04:00

When pushing new code there should be automated tests for core functions

logan added the

labels 2024-04-07 18:00:13 -04:00

logan added this to the Minimum Release milestone 2024-04-07 18:00:17 -04:00

logan commented

2024-04-14 17:30:52 -04:00

Initial automated tests have been made for the server and pdab handler, need to make a test for the socket client and then all core functions are being tested on push

logan referenced this issue from a commit

2024-04-21 14:57:28 -04:00

#10 #33 Update client setup and setup test

logan commented

2024-04-21 16:06:39 -04:00

for automated testing of the setup, I think we should setup a raspberry pi with a filesystem in memory (read/only) and use that from a github action.

This way we can test for real on a Pi, but each time it's tested, we can reset to a clean state to retest next time.

for automated testing of the setup, I think we should setup a raspberry pi with a filesystem in memory (read/only) and use that from a github action. This way we can test for real on a Pi, but each time it's tested, we can reset to a clean state to retest next time.

logan commented

2024-05-16 22:18:18 -04:00

Testing for server is done, client is a bit trickier. Working on just the socket client interaction with the server

Interaction with PDAB is trickier but could be done

Testing for server is done, client is a bit trickier. Working on just the socket client interaction with the server Interaction with PDAB is trickier but could be done

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: logan/DRBv3#33