Testing Tutorials
Guides and write-ups on software testing and automation, gathered from the blog's tutorial category. The material leans toward practical, tool-focused walkthroughs rather than theory, written by Łukasz Rosłonek for testers and developers looking to sharpen their day-to-day skills.
Automation Tooling
Selenium and Protractor feature as the core automation topics covered in this category.
- Selenium-based approaches to browser test automation.
- Protractor guides aimed at end-to-end testing scenarios.
Agile Methodology
Tutorials that connect testing practice with agile team workflows.
- Working testing activities into agile sprints and ceremonies.
- Balancing manual checks with automated coverage in fast-moving teams.
Microservices Testing
Strategies aimed at distributed, service-oriented architectures.
- Approaches for testing individual microservices in isolation.
- Considerations for verifying behavior across service boundaries.
These tutorials sit alongside the main blog and its contact page. For background on the author and the blog's history, see the Contact and Media page.
Tutorials gathered under the tutorials category focus on the practical side of software testing, leaning toward hands-on walkthroughs that readers can apply directly to everyday work. Rather than dwelling on abstract theory, the material emphasizes tool usage, configuration patterns, and small reusable recipes that fit into real engineering workflows. Each guide is written with testers and developers in mind, aiming to shorten the learning curve for common automation tasks and reinforce habits that lead to more reliable day-to-day results across diverse projects and team setups.
Browser-based automation receives substantial attention through dedicated coverage of Selenium and Protractor, the two flagship frameworks in this space. Selenium tutorials walk through element interaction strategies, wait handling, and structuring tests so they remain readable as suites grow. Protractor guides complement that coverage with end-to-end scenarios oriented around single-page applications, focusing on synchronization between test code and the dynamic interfaces being exercised, along with patterns that keep asynchronous steps from undermining test stability over time.
Beyond UI automation, the tutorials also explore tooling that supports the wider delivery process, including libraries commonly used for asynchronous testing, retry logic for flaky scenarios, and mocking frameworks that simulate external services. Walkthroughs on WireMock and similar tools show how teams can isolate components during integration work, while pieces on Spock and JUnit discuss expressive ways to structure test logic. The goal is to give readers a broader toolkit for shaping resilient, repeatable automated checks across varied application architectures.
Agile methodology appears as a recurring thread, connecting testing practice with the rhythms of iterative delivery. Tutorials in this area look at how quality assurance fits into sprint cycles, how testing responsibilities distribute across cross-functional teams, and how automation investments can be prioritized alongside feature development. By framing tests as part of continuous delivery rather than a separate phase, the writing encourages readers to embed verification deeply into their engineering culture and adapt their approach as systems and processes evolve.