Answers

1. Right now, our test pipeline relies on Diesel to do the migrations. We could simply build our own SQL scripts, housed in directories that define our version with a version table in the database. This would completely decouple our testing pipeline from the server that we are testing. If the server has the same endpoints and access to a PostgreSQL database, it can be tested using our pipeline, no matter what language the server is coded in.
2. If the module is simple with a good interface, we can merely copy it over and import it where we want to use it. If the module relies on advanced functionality with the framework, we must delete the trait implementations for the framework and implement traits for the new one.
3. We need to note that our test pipeline ran the Rocket server without any alterations. This is because we are using the same config and using Cargo to build and run the application. We would merely just have to point our build to the Rocket application and...