Games, code & testing

My projects.

Games I made, websites I built and problems I found. Open a project or read a test report.

Games on SteamQA reportsPDF resumes

Recruiter documents

My PDF resumes.

My resume

Open a PDF, or go to my resume page for a short summary.

You can always open my resume PDF ↗.

Loading current CVs…

The documents will appear here in a moment.

Game projects

Games I made and tested.

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

Released on Steam · Python

N-OS: Desktop Story

A story game inside a retro computer. Open apps, move windows and explore virtual files. Built with Python.

  • 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 clicker game with upgrades, mini-games and secrets. I tested saved progress, menus, achievements, translations and builds for Windows and macOS.

  • 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.

Send a short message in any language. I may add it to the N-OS Community Archive in the Developer Support Pack.

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

Test reports

Real bugs. Clear reports.

These are real problems from my games. Open a report to see the steps, fix and test results.

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
Read full case study
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
Read full case study

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

How I test software.

01

Manual testing

Try features, look for unexpected problems and check that updates do not break things.

02

UI and localization

Check menus and translations. Make sure text fits and each screen is easy to use.

03

QA support scripts

Write small Python scripts to check game logic and repeat simple tests.

Web work

Websites that work on phones and computers.

I build and update small websites. I check their layout, text, links and contact forms on phones and computers.

Open Gibrid-S