| ... | ... | @@ -71,6 +71,7 @@ Monogame Unit testing proved to be difficult since the reference material was pr |
|
|
|
* Nunit
|
|
|
|
* PyUnit
|
|
|
|
* MariaDB
|
|
|
|
* MySQL
|
|
|
|
* Character animator
|
|
|
|
* Adobe photoshop
|
|
|
|
* Ezgif.com
|
| ... | ... | @@ -87,7 +88,7 @@ Monogame Unit testing proved to be difficult since the reference material was pr |
|
|
|
* Nunit
|
|
|
|
* Jest
|
|
|
|
* PyUnit
|
|
|
|
* MariaDB
|
|
|
|
* MySQL
|
|
|
|
* Character animator
|
|
|
|
* Adobe photoshop
|
|
|
|
* Ezgif.com
|
| ... | ... | @@ -122,7 +123,7 @@ Original idea was to use C++ or Go for the gRPC programming, but after the gRPC |
|
|
|
|
|
|
|
gRPC was pretty much done after the first sprint, but it has been remade multiple times during the project to accomodate new way of sending data and what was needed in the database.
|
|
|
|
|
|
|
|
gRPC is running as a server on one of our salvaged PCs and every game view and even beacon scripts connect to it to get data needed to work together as a system.
|
|
|
|
gRPC is running as a server on one of our salvaged PCs and every game view and even beacon scripts connect to it to get data needed to work together as a system. Data was originally stored in MariaDB, but after some issues with sequelize it was changed to MySQL after MariaDB parts of the code stopped working.
|
|
|
|
|
|
|
|
Jest was used to unit test over 80% of the code in gRPC.
|
|
|
|
|
| ... | ... | |
| ... | ... | |