I am an Electrical engineer turned Software tester from Sydney.
Passionate about exploratory testing, PKM,
healthy lifestyle, learning and music.
Check out my articles, portfolio projects and social media accounts.
Let’s connect🙂.
What I Do
Testing leads to failure, and failure leads to understanding
-Burt Rutan.
Functional testing
I am am passionate about exploratory testing and I know how to write scripted test cases too. To achieve desired test coverage I analyse both explicit and implicit requirements, use different testing techniques, test scenarios, user personas, positive, neagtive testing and testing heuristics. I love visualise testing using mindmaps and diagrams.
API / Web Services
With the rise in cloud applications and interconnect platforms, API testing is a necessity. I am beginner in API testing but I know the basics of HTTP protocol, Authentication, Authorization, API methods, API testing types and vulnurabilities. I have some experience performing simple REST web services testing using Postman and Tavern (Python plugin). I constantly improve my API skills by practicing using API tools.
Manual testing
As a manual tester, I can provide fast and accurate visual feedback. Exploratory testing does not require time-consuming planning and preparation. It gives a human perspective on the look and feel of a software product and helps to verify compliance with the defined business requirements.
Test Automation
I have hands-on experience developing web UI tests using Python, Pytest and Selenium Web Driver. I am familiar with the basics of Git and GitHub, able to use Unix command-line interface. I am also familiar with the basics of CI/CD and has experience setting up Web UI tests using Jenkins and AWS EC2.
Mobile Testing
Today, most users access the Internet from mobile devices anytime, anywhere. I can help you to check compatibility, unstable functionality and UI rendering on iOS & Android to make sure that your software product provides the best experience possible to every potential customer.
Quality Bug Reports
The key goal of the bug report author is to provide high-quality information, to help stakeholders make wise decisions about which bugs to fix. Title, issue type, priority, environment, action performed and attachments (screenshots, videos and logs) – I will make sure that all elements and fields form well written and clear bug reports.
Recent Posts
-
Test Automation Tools: Cypress, Playwright, TestComplete Comparison Example
In this article, I wanted to share my experience with choosing and comparing modern UI test automation tools. It is important to note that I had no previous experience implementing test automation in a QA team. I had a lot of questions when, as a team, we initiated the process of setting up a test automation project from scratch. I learned some things along the way. This post is a
-
Takeaways – Technical web testing 101 Course by Alan Richardson
This post is a short reflection mostly for myself. I hope it will help me to improve my testing using the things I learned in this course. Keep doing use browser dev tools for mobile testing use browser dev tools to monitor errors in console use browser network tab in dev tools to monitor errors, modify requests, use it in my bug reports Should do / do better / more
-
Experience Report: Localization Testing
This was my first experience in testing localization of a web app. In this blog post, I decided to capture some things I learned that I could use in the future. I included the most common types of issues related to translation, things that helped me to understand risks and expected behaviour, some useful links and examples of translation problems. Where to start 1.Understand testing mission and start asking question.
Questions?
Please visit About page to learn more or send me a message via contact form.