Web software, tests included.
I build custom websites, web applications and business software for companies, and I write the tests for it too. That way the delivered work can be changed safely later.
I mainly work for companies in Komárom-Esztergom county, Hungary, and I take on remote work elsewhere.
Last full check of this site
- SEO
- 34 pages
- WCAG 2.2 AA
- 0 violations axe, light + dark theme
- GDPR
- 0 third-party requests
- Lighthouse
- 100 · 100 · 100 · 100 mobile + desktop, 8 templates
- tests
- 3613/3613
PASS
Work
All work-
Personal project
klevi.hu
Quizzes, tools and games, free and without ads or trackers.
Technologies: HTML, CSS, JavaScript
-
Test automation
levikaldor.hu quality gate
One command that checks every page before a release, and stops the push if anything got worse.
Technologies: Astro, TypeScript, Playwright, axe-core, Lighthouse, Vitest
What I do
-
New website or web application
A business website, web shop, enquiry or booking form, client portal, admin system or calculator, from the database to the interface.
TypeScript, Astro, Vue, Supabase
-
Developing an existing system
If a system already works but is slow, outdated or hard to change: I first write tests for how it behaves now, then develop, fix and maintain it.
Bug fixing, modernisation, maintenance
-
Website audit
If you do not know how fast, accessible and search-friendly your site is: I measure it, rank the issues by importance, and fix them on request.
Lighthouse, axe, WCAG 2.2
-
Testing and QA
For development teams and agencies: automated tests for the critical flows, fitted into your existing CI process.
Playwright, Vitest
How I work
- 1. Understanding. Goals, users, requirements and acceptance criteria.
- 2. Design and development. In small, verifiable steps, so there is something to try out after each stage.
- 3. Verification. Automated and manual tests, fitted to the project and its risks.
- 4. Handover. Source code, tests, documentation, access and the next steps.
My principles
- Test first
- For every piece of logic I first write a test that fails, and only then the code that passes it. That proves each test checks what it should.
- What a machine can check, a machine checks
- Tests, accessibility rules and performance measurements run before every change goes out, not only at handover.
- Usable by everyone
- It has to work with a keyboard, a screen reader and a slow mobile connection. I check that from the first version.
- Data-minimal
- I handle only the data and use only the external services that are strictly needed. This site, for example, sends no request to any third party.
This runs before every release
The output for this site, shortened. A change only reaches the main branch when every line is green. If one fails, the push stops.
About the quality gate$ git push origin main
→ npm test ✓ 3613 tests
→ audit: SEO ✓ 34 pages
→ audit: axe light+dark ✓ 0 violations
→ audit: GDPR ✓ 0 third-party requests
→ audit: Lighthouse ✓ 100 · 100 · 100 · 100
push allowedDo you have a web project or an operational problem that software could make simpler? Describe it briefly and we can discuss a possible solution.
Discuss a project If you prefer to write an email: hello@levikaldor.hu