Work & QA evidence

Public products and practical QA proof.

Released Steam games, testing scope, interactive cases, report PDFs and the product work behind the claims.

Released productsQA reportsCurrent CVs

Recruiter documents

Current CV catalogue.

Recruiter overview

The list is managed live and adapts to any number of focused CV versions.

Loading current CVs…

The documents will appear here in a moment.

Game projects

Public products with real QA responsibility.

Duxastr Studio on Steam
N-OS Desktop Story artwork with a retro computer

Released on Steam · Python

N-OS: Desktop Story

A modular desktop/OS simulation with 300+ Python files, 240+ JSON files and dozens of connected applications.

  • Tested window management, drag-and-drop, virtual files, applications/processes, saves, achievements, story states and recovery.
  • Ran functional, exploratory, smoke, regression, UI, localization and build verification tests.
  • Created Python scripts to automatically validate selected logic, states and repetitive scenarios.
  • Integrated and tested Steamworks, achievements, DLC, release configuration and launch builds.
Open Steam pageCommunity DLC
Neuro Clicker gameplay window

Released on Steam · 10+ updates

Neuro Clicker

A released and maintained Steam game tested across progression, upgrades, mini-games, UI states, saves, achievements, localization and Windows/macOS builds.

  • Investigated internal and player-reported issues.
  • Verified reproducibility, retested fixes and ran targeted regression before updates.
  • Integrated and tested Steam Workshop functionality.
Open Neuro Clicker on Steam
N-OS Community Archive Google Form

Community feature

N-OS Community Archive.

I collect short messages from people in different countries and languages. Selected entries may become part of N-OS history and appear in the Developer Support Pack / DLC as a community archive.

  • Recommended length: approximately 250-500 characters.
  • Submissions may be edited or selected according to the form rules.
Submit a message

QA case library

Post-release bugs, clearly documented.

Short real cases from released games. Open a card to see the full report, test steps and verification.

N-OS: Desktop StoryCritical

Stage 10 stays blocked after the ICU reply.

A migrated save had the correct forum reply, but the story still asked the player to answer Morrow again.

NOS-POST-010WindowsFixed · Retested
Neuro ClickerCritical

A damaged backup can reset valid progress.

One broken save copy caused a full reset even when the second signed copy was valid and safe to use.

NC-POST-004Windows · Steam CloudFixed · Tests passed

More report samples

Rider iOS PDF ↗N-OS build PDF ↗
NOS-POST-010 · Post-releaseCritical

Stage 10 stays blocked after the ICU reply.

The player completed the required forum action, but the story did not move to the next step.

PriorityP0
StatusFixed · Retested
EnvironmentSteam · Windows 10/11
AreaSave migration · Story
Precondition

Use a save created before the update. Stage 10 is active.

Steps to reproduce
  1. Open ICU and reply to Morrow.
  2. Return to the Code Editor.
  3. Open build 10 and press Run.
  4. Restart the game and check the same stage.
Result
Actual

The game asks for the ICU reply again. Progress stays at stage 10.

Expected

The saved reply is detected and the next story step opens.

Root cause and fix

Old saves stored the reply in a legacy state key. The new story check only read the current key. Save migration now reads both formats and writes one current value. Running migration twice does not change progress.

Release result: Passed

The blocker was reproduced, fixed and checked with old and current save data.
NC-POST-004 · Post-release regressionCritical

A damaged backup can reset valid progress.

The game had two save copies, but one broken file could still cause a full progress reset.

PriorityP0
StatusFixed · Automated
EnvironmentWindows · Steam build
AreaSave recovery
Precondition

The player has progress. save.dat and save.bak were created by the game and have valid signatures.

Steps to reproduce
  1. Keep one signed save file valid.
  2. Replace the second file with partial data.
  3. Start the game and load progress.
  4. Repeat with the primary and backup files swapped.
Result
Actual

IQ and click progress return to zero. The save is marked as modified.

Expected

The game loads the valid signed copy and rebuilds the damaged file.

Root cause and fix

The loader treated one damaged copy as save tampering, even when the other copy passed its signature check. It now trusts the valid copy, keeps progress and writes a fresh pair of save files.

Regression result: Passed

Both recovery paths failed before the code change and passed after it.

QA coverage

What the projects demonstrate.

01

Manual testing

Functional, exploratory, smoke and regression testing across connected workflows and edge cases.

02

UI and localization

Wrong states, text overflow, truncation, context, layout and consistency across multiple languages.

03

Basic automation

Custom Python scripts for selected logic, state validation and repetitive checks - without claiming framework experience I do not have.

Web work

Product presentation and responsive UI.

I built and maintain portfolio and company websites, including structure, layout, content, links, responsive behavior and contact flows. This adds practical context for web UI and usability testing.

Open Gibrid-S