Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration tests #446

Open
PerchunPak opened this issue Dec 21, 2022 · 5 comments
Open

Integration tests #446

PerchunPak opened this issue Dec 21, 2022 · 5 comments
Labels
area: tests Related to unit-tests or other type of testing type: feature New request or feature

Comments

@PerchunPak
Copy link
Member

We should add some kind of integration tests on release, to prevent such issues as #433. On another hand, it would be hard work, and possibly will not find anything even in long term.

We also don't have unit tests for some parts of our code (like Bedrock part and CLI as well, partially tracked by #371).

@ItsDrike ItsDrike added type: feature New request or feature area: tests Related to unit-tests or other type of testing labels Dec 21, 2022
@kevinkjt2000
Copy link
Contributor

Running a few containerized Minecraft servers would be a way to tackle this. I recommend itzg's Minecraft docker images; I've been using those for a while to run servers and they work great. There's an image that runs bedrock too.

@PerchunPak
Copy link
Member Author

PerchunPak commented Dec 23, 2022

A list of server implementations to test.

Java ones (itzg's docker):

Bedrock (itzg's docker):

Proxies:

I tried to include all popular server cores. Maybe it's a lot, and we should cut some of them.

@ItsDrike
Copy link
Member

Could be worth including a forge server, or other modded server too

@PerchunPak
Copy link
Member Author

They're under PurPur.

@PerchunPak
Copy link
Member Author

PerchunPak commented Dec 11, 2023

Duplicating my messages from Discord for history.


I have just found that DigitalOcean provides free hosting for some open-source projects. We could try to apply and host there our integration tests
https://www.digitalocean.com/open-source/credits-for-projects

Although, they provide only $60/year (which is $5/month) and we probably could only buy 512mb RAM VPS

Another idea is to use swap, but it would drastically decrease speed (although if we would test so many versions and cores as we currently want, speed wouldn't really matter)

As it's integration tests are blocking for releases, we could leverage it by automatically creating patch notes (and so GitHub release) or by manually triggering integration tests before manually creating GitHub release

Any thoughts? If not, just add 👍 and I will email DigitalOcean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: tests Related to unit-tests or other type of testing type: feature New request or feature
Projects
None yet
Development

No branches or pull requests

3 participants