Mechi Test Kit

Do this

1. 1Keep tests.mechi.club open as your checklist, then open mechi.club and mechi.lokimax.top in separate tabs.
2. 2Sign in or prepare one fresh free player, one second player, one Pro or Elite player, one banned account, and one admin account in separate browser sessions.

Pass if

• You can switch between all required accounts without logging anyone out accidentally.
• Each host opens the correct surface and stays on its own domain.

Do this

1. 1Open landing, pricing, and the legal pages on a wide desktop viewport and scroll each page from top to bottom once.
2. 2Click the primary CTA on each surface and confirm back and forward navigation still feel normal.

Pass if

• There is no broken spacing, clipped copy, missing art, or dead CTA on the first public pass.
• Host-specific pages stay on the correct domain instead of cross-routing unexpectedly.

Do this

1. 1Switch to a narrow mobile viewport and check landing, register, login, and dashboard.
2. 2Open menus, tap primary buttons, and interact with at least one form field on each page.

Pass if

• There is no horizontal scroll, impossible tap target, or clipped modal on mobile.
• Sticky bars, cards, and forms remain readable and usable on a narrow screen.

Do this

1. 1Open the landing page and scan hero, feature blocks, rank content, and footer.
2. 2Use the main CTA and at least one secondary CTA in separate tabs.

Pass if

• The page feels intentional and complete, with no missing sections or placeholder content.
• Primary navigation and footer links land on real Mechi pages.

Do this

1. 1Open pricing and compare all visible plans, feature lists, and CTA buttons.
2. 2Try the upgrade CTA from pricing and confirm the next screen matches the chosen plan.

Pass if

• Plan labels, benefits, and upgrade messaging do not contradict each other.
• The selected CTA points to the correct follow-up step instead of a dead or unrelated route.

Do this

1. 1Open the three legal pages in separate tabs and scan headings, body copy, and footer or sibling links.
2. 2Use any cross-link between the legal pages once.

Pass if

• Each legal page has real content, clean structure, and no broken formatting blocks.
• Links between legal surfaces still work and do not dump the user onto the wrong host.

Do this

1. 1Generate a real invite from a logged-in player, then open the resulting join link in a fresh anonymous tab.
2. 2Also try a malformed or expired join code and observe the fallback state.

Pass if

• A valid invite leads the user into the correct join, login, or register path with clear next steps.
• A bad code fails safely and never white-screens or traps the user.

Do this

1. 1Complete the registration wizard with profile basics, game selection, platform IDs, and the WhatsApp notification preference.
2. 2Finish the flow and let the app redirect into the signed-in experience.

Pass if

• The new user lands in the app with the chosen games, profile details, and alert preference reflected cleanly.
• Validation is understandable and no step in the wizard silently drops the user input.

Do this

1. 1Log in with a healthy existing player account using at least one of the supported sign-in methods now exposed on the page, then visit dashboard, profile, and one more protected page.
2. 2Refresh the browser on a protected page once after login.

Pass if

• The user reaches the protected app without redirect loops.
• Refresh does not drop the session or produce a blank loading state, regardless of the login method used.

Do this

1. 1Use email sign-in, enter the matching username and email, and confirm the player signs in without a password or email link.
2. 2Use forgot-password or reset-password, enter the matching username and either the account email or phone number, then complete the inline password reset flow.

Pass if

• Magic-link email still lands with a working Mechi link.
• The password reset flow unlocks the new-password step only after the username and account contact match, then signs the player in or lets them log in with the new password.

Do this

1. 1Attempt login with a banned user account and try to reach a protected route afterward.
2. 2Open the banned state directly once so the message and support direction can be reviewed.

Pass if

• The banned user cannot enter protected app pages.
• The blocked state is explicit and does not look like a generic auth failure.

Do this

1. 1Open dashboard after login and compare queue, active match, quick actions, and profile summary areas.
2. 2Refresh the dashboard once after some other action such as queue join or profile edit.

Pass if

• The dashboard reflects the current account state instead of stale or conflicting summaries.
• Quick actions and counts feel connected to the rest of the app.

Do this

1. 1Open the games page, add or update at least one supported title, and save the correct platform ID.
2. 2Leave the page and return to confirm the saved setup persists.

Pass if

• Saved games and IDs reappear after refresh without validation glitches.
• Plan limits or game-selection gates behave as designed for the current account.

Do this

1. 1Open profile and scan rank, summary, achievements, and any share or edit actions.
2. 2Compare one visible stat or badge with the latest match or account state you expect.

Pass if

• Profile content looks intentional and not partially loaded or contradictory.
• Visible rank or summary data matches the account you are testing.

Do this

1. 1Change one or more fields on profile settings such as location, bio, or supported-game preferences.
2. 2Save the form, refresh, and confirm the new values still appear.

Pass if

• Changes persist after refresh and validation stays readable.
• The saved settings propagate back to profile and any other visible summary surface.

Do this

1. 1Upload a new avatar or cover image, use the cropper if presented, and save the result.
2. 2Open profile and profile settings again to verify the image appears in both places.

Pass if

• Upload, preview, crop, and save all complete without broken thumbnails.
• The final media displays at the right size instead of stretching or disappearing.

Do this

1. 1Open notifications and scan timestamps, empty states, and any CTA tied to WhatsApp or another follow-up action.
2. 2Refresh once and verify the list does not collapse into duplicate or missing cards.

Pass if

• Notifications render as real activity instead of placeholders or empty shells.
• Any CTA opens the correct destination when that action is configured.

Do this

1. 1Open share center and use at least one copy or open action for a personal or referral link.
2. 2Paste the copied value into a fresh tab or note area and confirm it looks like a real Mechi URL.

Pass if

• Generated links are well formed and point to the right destination.
• Share actions do not silently fail or copy malformed values.

Do this

1. 1Open leaderboard and try any available game or rank filter.
2. 2Compare at least one visible identity, rank, or ordering clue with the latest test account state.

Pass if

• The leaderboard loads without broken filtering or empty-shell rows.
• Filtering and account context feel plausible for the selected game.

Do this

1. 1Open profile settings, pick one supported snapshot game such as eFootball, CODM, or PUBG Mobile, and upload an in-game screenshot.
2. 2If a snapshot already exists, replace it once, then refresh the page and confirm the updated image is still attached to the right game card.

Pass if

• Snapshot cards accept uploads without broken previews, stuck loading overlays, or wrong-game placement.
• The saved snapshot remains visible after refresh and can be removed or changed cleanly.

Do this

1. 1Open queue for a configured game, join matchmaking, and wait until the searching state is visible.
2. 2Cancel the search and return to dashboard or queue once more.

Pass if

• Queue entry shows a believable searching state with no duplicate banners.
• Cancel removes the player cleanly and syncs with dashboard or queue status.

Do this

1. 1Put two compatible players into queue and let the normal matching flow or safe manual trigger create the match.
2. 2Check both accounts as soon as the handoff happens.

Pass if

• Both players land on the same live match and leave the queue state behind.
• The resulting match feels singular and synchronized instead of duplicated or split.

Do this

1. 1Create a direct challenge from one player and open the challenges surface on both accounts.
2. 2Accept once with Player B, then repeat with a second challenge and decline it.

Pass if

• Challenge state updates on both accounts without stale cards lingering behind.
• Accept and decline produce different, understandable outcomes.

Do this

1. 1Open the same live match on both accounts and exchange chat messages in both directions.
2. 2Observe timer or status panels before and after one refresh.

Pass if

• Messages arrive without duplicates or silent drops.
• The match page still shows a coherent live state after refresh.

Do this

1. 1Open a live match, upload any evidence or screenshot if the flow supports it, and report a matching winner from both accounts.
2. 2Wait for the match to settle, then review the final state.

Pass if

• Evidence upload completes without broken previews or missing files.
• Matching reports resolve the match cleanly and move it out of the live state.

Do this

1. 1Repeat a match result flow with conflicting winners or use the available escalation action.
2. 2Check the player-facing status after the disagreement is submitted.

Pass if

• Players see a clear disputed or escalated state rather than a hidden failure.
• The match remains actionable for the admin lane instead of disappearing.

Do this

1. 1After a match settles, revisit dashboard, profile, leaderboard, and any visible rank summary.
2. 2Compare the updated state with the winner and loser you just tested.

Pass if

• Recent results feel reflected across the player surfaces that depend on them.
• There is no obvious stale data conflict between match result, dashboard, and profile summaries.

Do this

1. 1Open lobbies and switch any visible game filter or status view.
2. 2Scan room cards for member counts, privacy labels, and join affordances.

Pass if

• The lobby feed loads without empty-shell cards or broken filters.
• Privacy, game, and occupancy cues look trustworthy on the list.

Do this

1. 1Create one public lobby and one private lobby with real game settings.
2. 2Return to the lobby list and confirm each room appears with the right visibility rules.

Pass if

• Room creation succeeds without duplicated or malformed entries.
• Public and private visibility behave differently in the way the product intends.

Do this

1. 1Join a created lobby with a second player using the list or any invite path.
2. 2Verify host controls, member counts, and leave or close behavior from the room detail view.

Pass if

• Both players see consistent member presence and room identity.
• Host and non-host actions behave differently in the expected way.

Do this

1. 1Open tournaments, move through the visible tabs or states, and then open one real tournament detail page.
2. 2Compare the detail page status, player counts, and labels with the list card.

Pass if

• Tournament status labeling is consistent between list and detail.
• The detail page loads real rules, players, or bracket context without layout issues.

Do this

1. 1Try tournament creation with a free account, then repeat with a higher-tier account if available.
2. 2Review any fee or upgrade explanation shown during setup.

Pass if

• Plan-gated behavior is explicit instead of surprising or silent.
• Free, paid, or upgrade messaging stays consistent with pricing expectations.

Do this

1. 1Join the tournament with enough players to start it, then use the organizer controls to begin.
2. 2Advance at least one round using the available result flow and observe bracket updates.

Pass if

• Join and start actions move the tournament into the expected next state.
• Bracket or round progress updates cleanly after results settle.

Do this

1. 1Open an active tournament as an Elite organizer, Elite participant, or admin and use the Go Live flow to create the stream.
2. 2Copy the returned RTMPS URL and stream key into OBS or Larix, start streaming, and watch the tournament card, detail page, and /t/[slug]/live page update.
3. 3Open the live page from a second signed-in account and confirm the player loads for authenticated users only.

Pass if

• The tournament list and detail surfaces show a LIVE state once Mux marks the stream active.
• Signed-in viewers can watch the stream on /t/[slug]/live while signed-out users are redirected to login.
• The streamer can stop the stream cleanly and the page falls back to ended or replay state after webhook processing.

Do this

1. 1Keep the stream live for more than ten minutes, send at least one viewer heartbeat by watching from a signed-in account, then stop the stream.
2. 2Wait for Mux to emit the idle and live_stream_completed events, then refresh the streamer and viewer surfaces.
3. 3Check rewards, replay availability, and any operational logs or database traces you use during launch verification.

Pass if

• Viewer RP accrues in 10-minute blocks without exceeding the 20 RP daily cap across streams.
• The streamer receives the go-live bonus once for a qualifying session longer than ten minutes.
• The replay becomes available on the live page after the finalized recording webhook arrives.

Do this

1. 1Open rewards and scan summary balances, ways to earn, catalog items, and recent activity.
2. 2Refresh after one action if any reward-related action is available on the page.

Pass if

• The page renders as one coherent rewards surface rather than partial fragments.
• Balances, catalog items, and activity do not visibly contradict each other.

Do this

1. 1Redeem a safe partner reward from the Mechi rewards catalog with a test-ready account.
2. 2Refresh rewards after redeeming and confirm the status stays visible without sending the player to an external orders page.

Pass if

• The reward redeems on Mechi without a manual account-link step.
• The redemption state and fulfillment progress are reflected on Mechi without an external handoff.

Do this

1. 1Create a new suggestion from one account, then vote on it from another account.
2. 2Refresh the suggestion list on both accounts after the vote lands.

Pass if

• The new suggestion appears quickly and keeps a stable identity after refresh.
• Vote behavior is clear and does not produce duplicate state or phantom counts.

Do this

1. 1Start an upgrade from pricing or another gated surface and follow the Paystack handoff using a reversible test path.
2. 2Exercise one successful or safe completion path and one cancel or return path if possible.

Pass if

• Selected plan, checkout handoff, and return state stay consistent across the flow.
• Cancel or retry behavior is understandable and does not strand the user.

Do this

1. 1After any plan change, revisit dashboard, profile settings, pricing, and a gated surface such as tournament creation.
2. 2Compare what each surface says about the current plan or entitlement.

Pass if

• The visible plan name or gating state is consistent across the app.
• The user no longer sees stale free-plan restrictions if the upgrade succeeded.

Do this

1. 1Open bounties, review the live challenge cards, then expand the claimed history section once.
2. 2Refresh the page and compare the live count, claimed winners, and payout language for any stale or contradictory state.

Pass if

• Active bounties load as deliberate challenge cards instead of empty placeholders or broken sections.
• Claimed history expands cleanly, winner states feel plausible, and the payout copy stays consistent across refresh.

Do this

1. 1Generate a player share URL from the signed-in app and open it in an anonymous tab.
2. 2Compare the public card with the latest profile details for that user.

Pass if

• The public profile loads without auth and shows the right user identity.
• Layout, metadata, and visible stats feel deliberate and not half-rendered.

Do this

1. 1Generate a public match URL from a real completed or live match and open it in an anonymous tab.
2. 2Compare the winner, game, and visible summary with the underlying match.

Pass if

• The public match page loads without auth and reflects the right match identity.
• The surface looks complete enough to share externally.

Do this

1. 1Open a generated public tournament URL from a real tournament in a fresh anonymous tab.
2. 2Compare tournament status, participants, or bracket clues with the signed-in tournament page.

Pass if

• The public tournament page loads without auth barriers.
• Public-facing tournament information stays aligned with the current tournament state.

Do this

1. 1Move between tests, the main app, and admin using fresh tabs plus direct URL entry.
2. 2Verify one player route, one admin route, and one public route on their intended hosts.

Pass if

• Main app routes stay on mechi.club and admin stays on mechi.lokimax.top.
• No host redirects the user into the wrong product surface unexpectedly.

Do this

1. 1Open the admin home directly on mechi.lokimax.top and move through the primary navigation once.
2. 2Compare at least one KPI or attention lane with another admin detail page.

Pass if

• Admin navigation is stable and clearly distinct from the player app.
• Overview cards show meaningful operational data instead of empty placeholders.

Do this

1. 1Search for a known player, open the detail pane, and inspect account, plan, and recent activity sections.
2. 2Perform one safe moderation action such as ban, unban, or role update if your test environment allows it.

Pass if

• Search returns the correct user quickly and detail panels load without stale shells.
• Moderation actions acknowledge success and update the visible account state after refresh.

Do this

1. 1Open the queue admin lane, use search or filters, and inspect a real waiting entry.
2. 2If a safe reconcile action exists, run it once against a controlled test scenario.

Pass if

• Queue filters return believable results and entry cards stay readable.
• Operational actions refresh the lane instead of leaving stale queue state behind.

Do this

1. 1Open a real match record, especially one from a disputed or escalated flow if available.
2. 2Review the detail view and exercise one safe admin action or reply path.

Pass if

• The match detail loads enough context for a decision.
• Admin actions update the match record and leave a coherent player-facing state.

Do this

1. 1Open both the tournaments and lobbies admin pages, then inspect at least one real record on each.
2. 2Use one safe moderation or review action if the environment supports it.

Pass if

• Both lanes load meaningful records and detail views without broken UI.
• Moderation affordances are visible and behave predictably after refresh.

Do this

1. 1Open admin rewards, use the available filters, and inspect at least one review item.
2. 2Perform one safe approve, reject, or note action if your test path allows it.

Pass if

• Review items expose enough context to make a decision.
• Resolution actions refresh the record cleanly without leaving a mismatched status.

Do this

1. 1Open support, load a real thread, and inspect its transcript plus any status controls.
2. 2Send one safe reply or status update and then refresh the thread.

Pass if

• Messages render in order and the new reply appears exactly once.
• Thread status stays readable after refresh instead of reverting or duplicating state.

Do this

1. 1Open WhatsApp ops, Instagram ops, and logs in separate tabs and inspect the main controls or log output.
2. 2If a safe preview or test-send path exists, use it once without contacting a real user unintentionally.

Pass if

• Each operational page loads enough state to be usable by a human operator.
• Logs render with readable entries and comms surfaces do not break when refreshed.

Do this

1. 1Open admin bounties, create one safe draft, and confirm it appears in the control room with the expected trigger, prize, and week label.
2. 2If the environment already has a controlled bounty, test one lifecycle action such as Go Live, Cancel, or Mark Paid and then refresh the lane.

Pass if

• Draft creation returns a visible bounty card with the right metadata instead of a silent failure.
• Lifecycle actions update status cleanly after refresh and do not leave the bounty in a contradictory payout state.