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
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
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.
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
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
When pushing new code there should be automated tests for core functions
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
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.
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