# Filip Hric - Test Automation Expert

> Filip Hric is a freelance DevRel, consultant, tester and developer. He teaches testers about web development and developers about testing. Filip is an international keynote speaker and one of the leading experts on test automation in Cypress.io. He's an author of several Cypress workshops and has taught hundreds of testers and developers around the world how to effectively use Cypress and apply good practices in web test automation.

## Connect with Filip

- Twitter/X: https://twitter.com/filip_hric
- LinkedIn: https://www.linkedin.com/in/filip-hric
- Bluesky: https://bsky.app/profile/filiphric.com
- GitHub: https://github.com/filiphric
- YouTube: https://www.youtube.com/@filip_hric
- Discord: https://discord.com/invite/3MdvPfT
- Email: filip@filiphric.com
- Schedule a call: https://cal.com/filiphric

## Key Pages

- [Blog](https://filiphric.com/blog): Technical articles on test automation
- [Workshops](https://filiphric.com/workshops): Live Cypress workshops
- [Courses](https://filiphric.com/courses): Online learning resources
- [Company Consulting](https://filiphric.com/company-consulting): Testing culture and DevRel consulting
- [Individual Tutoring](https://filiphric.com/individual-tutoring): 1-on-1 mentoring sessions
- [About](https://filiphric.com/about): More about Filip

## Featured Blog Posts

### Cypress Fundamentals
- [Cypress basics: Using baseUrl](https://filiphric.com/cypress-basics-using-baseurl): Setting up `baseUrl` helps you write your test in a way that enables running them against multiple environments. This is vital to make your tests available for multiple versions of your app.
- [Cypress basics: Uploading a file](https://filiphric.com/cypress-basics-uploading-file): Short explanation on how to upload a file with Cypress to a drag and drop element, inputs or directly by calling your API
- [Cypress basics: API testing](https://filiphric.com/cypress-basics-api-testing): Cypress is a great testing tool that can be also very helpful when testing API. In this post, I’ll go over some basics on how to write an API test in Cypress.
- [Cypress basics: Variables](https://filiphric.com/cypress-basics-variables): How to store variables in Cypress tests and use variables and aliases inside the test and between tests.
- [Cypress basics: xpath vs. CSS selectors](https://filiphric.com/cypress-basics-xpath-vs-css-selectors): Using xpath with Cypress is possible through a plugin. In this post I show you how to install this plugin and show you some examples how to use xpath and compare it to Cypress commands.

### Playwright
- [10 Tips for Writing Playwright Tests with Cursor](https://filiphric.com/cursor-playwright-tips): Practical tips gathered from months of writing Playwright tests with Cursor. Learn how to use project rules, workflows, screenshots, and MCP for better test automation.
- [2FA testing with Playwright and Mailosaur](https://filiphric.com/2fa-testing-with-playwright-and-mailosaur): Learn how to automate email magic links, SMS verification codes, and authenticator app logins in Playwright using Mailosaur for comprehensive authentication testing.

### Vitest & Unit Testing
- [Introduction to testing in Vitest](https://filiphric.com/introduction-to-testing-in-vitest): A comprehensive guide to Vitest testing framework, covering its core features, capabilities and practical examples for unit and component testing

### Additional Resources
- [How to structure a big project in Cypress](https://filiphric.com/how-to-structure-a-big-project-in-cypress): Opinion on how a project with +2000 tests should be structured in order to achieve good maintainability, speed and lower the risk of introducing regressions.
- [8 common mistakes in Cypress (and how to avoid them)](https://filiphric.com/8-common-mistakes-in-cypress-and-how-to-avoid-them): In this blogpost I’m sharing a couple of testing antipatterns that can make your test flaky, hard to read or slow.
- [Maslow's Hammer and Three Lies QA Tells Itself](https://filiphric.com/maslows-hammer-and-three-lies-qa-tells-itself): A short post on what needs to change for QA to thrive in the age of AI.
- [AGENTS.md Files Are Not Misleading Your AI Agent](https://filiphric.com/agents-md-files-are-not-misleading-your-ai-agent): A recent study sparked headlines claiming AGENTS.md files hurt AI agent performance. But the full picture tells a different story - human-written context files actually improve results by 4%.
- [Don’t let A.I. read your .env files](https://filiphric.com/dont-let-ai-read-your-env-files): Stop storing API keys and database passwords in plain text .env files. Learn how to use 1Password CLI to inject secrets at runtime for better security.
- [How I automated the annoying part of my job with Goose and Playwright MCP](https://filiphric.com/how-i-automated-the-annoying-part-of-my-job-with-goose-and-playwright-mcp): Learn how to automate repetitive issue creation tasks using Goose desktop app and Playwright MCP. Stop context switching and let AI handle the boring stuff.
- [Testing Will Become More Important, Not Less](https://filiphric.com/testing-will-become-more-important-not-less): LLMs speed up coding but quality concerns remain. Testing becomes more crucial, evolving to include AI-generated tests while human expertise in test design stays valuable.

## Optional

For complete blog archive: https://filiphric.com/llms-full.txt
RSS Feed: https://filiphric.com/rss.xml
Sitemap: https://filiphric.com/sitemap.xml