-
Notifications
You must be signed in to change notification settings - Fork 278
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
Tester Specs #1783
Comments
I would like to do testing. I will also be building a new computer in March with AMD Ryzen to replace my old broken desktop. |
I am watching this project for a while now and would love to help out OS: Win 10 |
Can't at the moment due to exams but after that I should be able to do some testing OS: Win 10 |
I would like to create a list of people who can test with some regularity, along with applicable specs, as it would be beneficial for some PRs (#1781 for a current example) to be tested either across a range or at extremes.
This is for targeted testing (answering a specific questions such as "Is this UI too big/small at certain resolutions" or "Does this significantly hamper/enhance performance on low-end computers"), coding ability is not required, being able to compile the project is a huge plus, but there are situations where it may not be required (testing performance on an extremely low-end computer that for whatever reason is incapable of compiling the project or doing so is difficult for one reason or another). This particular sort of testing doesn't need to be extensive (it doesn't have to tell if something is working right or breaks things), and in most cases should be as simple as running the project and seeing how things look, and at most giving a few orders and seeing how things run, or panning the screen around or other simple tasks.
Now for what I think is needed (if multiple computers are available, list each separately):
The text was updated successfully, but these errors were encountered: