Tester Handbook.

Testers catch problems before players do. A good bug report is one of the most valuable things anyone can give a game team, and at Lucky 7 testers get builds early and have a real say in whether they are ready.

• Testers are players who help bug test new builds and updates. No experience is needed, just patience and attention to detail.
• QA Testers bring structured testing: regression passes, balance testing and detailed reports.
• QA Leads own test plans, triage and release sign-off.
• Localization Testers check language and regional details across builds.

Testers are part of the team, so the Staff Handbook applies to you as well.

• Test only in the build, server or session you have been given for testing.
• Never test unreleased content in a public server unless you have been told to.
• Do not change place settings, publish anything, or invite people who are not testers.
• Check the list of known issues before you start, so your time goes on new problems.
• Scheduled test sessions are announced in advance. Join the ones you can; there is no penalty for missing one.

• Functionality. Does the feature work as described? Test the expected behavior first, then try unusual or unexpected things.
• Performance. Does it lag, stutter or slow down over time? Try it with few players and with many when you can.
• Exploits. Is there a way to abuse a mechanic, get an unfair advantage or get past a restriction? Report it privately; never share an exploit.
• Visuals. Does it look right on different screen sizes and devices, and does it match the reference?
• Audio. Do sounds play at the right moment, at a sensible volume, without gaps?

The more specific the report, the faster it gets fixed. Every report should cover:

1. A short, specific title. "Tower sells for 0 after upgrade" beats "selling broken".
2. Which game and which build.
3. What you were doing, what happened, and what you expected to happen instead.
4. Steps to reproduce it, as exact as you can make them.
5. How often it happens: always, sometimes or once.
6. Your device, and any settings that might matter.
7. A screenshot or recording, where you are allowed to take one for the team.

One bug per report. Stay factual and leave frustration out; the report is about the bug, not the people who wrote the code.

"No issues found" is a valid and useful result. Say so explicitly when a test pass comes back clean.

Choose severity honestly. It decides what gets fixed first.

• Critical. The game crashes, data or progress is lost, players cannot progress at all, or there is a major unfair advantage. Report it immediately.
• High. A major feature is broken or out of reach, or the bug affects many players or core gameplay.
• Medium. The feature works but has a noticeable problem, or there is a workaround.
• Low. Cosmetic, minor or edge case only, such as a typo or a small visual glitch.

Every report is read. The development team marks it as acknowledged when it has been looked at, fixed when the fix is in, or will not fix when it is working as intended or not worth the risk of changing. Your reports and their status stay visible to you, so you can see what came of them.

Everything you see in testing is confidential: builds, new mechanics, unreleased characters, maps and music. Do not stream, record for anyone outside the team, screenshot for social media, or describe unreleased content publicly.

This applies to other Lucky 7 team members who are not on the same project, unless you have been told otherwise. Test builds and their links are for you alone; never pass them on.

If a leak happens, tell us straight away, even if it was an accident. Leaks are much easier to contain early.

Testers are often also players in our community, and other players will see you as part of the team. Do not use test access to gain an advantage in a live game, do not hint at unreleased content, and keep feedback about the game respectful and constructive.

Tester roles are listed on our open roles page when we are recruiting. Testing roles are volunteer roles. Applicants must be at least 16, and anyone under 18 needs a parent or guardian's consent before starting.

If you are a player who has found a bug in a released game, you do not need to be a tester to report it: use our public bug report form.

This is the public edition of the Tester Handbook. Staff can read an internal edition, which adds the tools, procedures and contacts behind each section, from their dashboard after signing in.

Where this handbook and your signed contract or agreement say different things, your contract or agreement is what applies. Pay, payment timing and the terms of your engagement are covered in your contract or agreement, not here.

We review the handbooks when the way we work changes. Each edition carries a version number and the date it was last updated, and a change in substance gets a new version.

Questions about anything in it can go to support@lucky7entertainment.com.