We had created a mobile game testing checklist (in general) by mindmap that can help us organize the test ideas (test techniques, types of testing, types of risk, heuristics, oracles, …) and driving the testing effectively. Now, in this post, we would like to introduce how we apply it with a real mobile game in Android and present the final testing result as well. A hand-on mobile game testing with Meu Solutions.Continue reading
I’d like to share 4 big fears that I have met when I started my software testing career by applying ET approach. If you are encountering these, it may be helpful to read this article.
FEAR WHEN APPLYING
We know when applying exploratory testing (ET), it requires exploratory testers to build test models, use them with all skills, heuristics, practices to explore, reasoning questions, evaluate and find hidden things from what they test. With this approach, all tests are designed, executed, reported in parallel from rapid learning. But, this is just a theory! With Junior testers, when they start off their test, a lot of things appear such as: Where should we start the test? Which way to perform Exploratory Testing effectively not to be missed bugs?, How can we test without given test cases and lack of product knowledge?…etc. A lot of questions that make you confused, don’t worry these articles might help you To perform Exploratory Testing effectively, Effective Exploratory Testing (Part 2): More Effective With Pair Exploratory Testing.
This is a mobile game checklist list from Meu Solutions in the form of mindmap. This will help the tester to perform the testing on any generic mobile game testing on any platform. It will help the AUT (Application Under Test) passes all the check point from the below testing checklist before it is released […]Continue reading
Cem Kaner defines exploratory testing as “a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project.”
It’s undeniable to say that exploratory testing becomes more popular and more effective in an agile world. Some organizations have established their strategy to “evolve” their testers to be more “agile” by adopting & training on exploratory testing. When conducting the training at MeU Solutions and at seminars where I am invited as a guest speaker to introduce a “new approach” called “Context-Driven Testing”, usually I am asked the question “How to become an exploratory tester?”. In fact, testing is exploring, so tester is an explorer in testing. The correct question should be “How to be a great exploratory tester?”Continue reading
Pair Testing is an approach of software testing in which two persons sit together at the same time and place to carry out and design tests. Pair testing is a collaborative effort, versus a single-person effort. Usually, one person controls the mouse and keyboard to perform directly the tests, while the other person asks questions, takes notes, and brings more scenarios which support the testing better. When talking about pair testing, we usually imply that one tester and one developer to work together.
Session-based testing is a method to measure and manage & implement exploratory testing better. In session-based testing, the testing is limited in given timeboxes, typically 60’-120’ minutes long. Each test session has its specific goals and contains a specific portion of what needs to be tested. A session can be a UAT Test for a story, a screen, a bug, a business transaction, or a technology facing for a piece of feature.Continue reading