Testing techniques used for manual testing at Tester Work

The software testing industry has evolved to an unprecedented extent in the last decades. Plenty of test types and different methodologies/techniques were identified and described by the pioneers of this field. 

Here at Tester Work, we also apply several of them depending on the client’s requests and demands, however, based on the “keep it simple” uptake, these are usually blended into our usual test cycles without actually mentioning what sort of testing methodology has to be applied during a test.  

Below, we’ll present some of the most common test techniques you can meet and thus implement while testing with us:

• Smoke testing - involves the verification of the key functions of an application in order to determine if the build is stable enough for further, more in-depth testing purposes or a possible app release. The features which are included in this test vary on the structure of the app and also depend on the client's requirements. Such aspects are generally included, but not limited to: app launch, general UI functions, Settings, and access to the main content.

• Functional testing - is a testing type through which all the app features get to be tested and it ensures that the requirement specifications are met application-wise. A general functionality test can include almost every bug type, except those which are set to be out of scope by the test manager.

• Unit testing - as its name already suggests, the unit testing refers to the thorough verification of a certain individual part of the application. The purpose is to validate that each app unit is in concordance with the original design and functionalities and that it can be integrated into the system without generating errors resulted from the unit’s possible flaws.

• Stress test - is a testing activity under a heavy load, specifically created to analyze the app’s functionalities beyond the limits of normal operation. 

• Language checks or App localization - this testing method usually refers to the verification of the text’s correctness in a certain application on a target language, along with aspects such as text positioning, missing strings, untranslated/mistranslated words/lines and so on. You might be asked to provide the correct version of the text issue you found or to provide a more adequate translation to be in conformity with the context.

• Compatibility check - is used to determine whether an app is capable of running on different operating systems, platforms or network environments. It has a key role in crowdsourced testing, which is mostly defined by the large variety of platforms/devices involved during a test run.

• Usability testing - is widely applied to measure how user-friendly an application is and how easily it can be understood by the targeted end-users. Actually, this is not an easy task as every single individual has a different perception about the product mostly based on their skills and level/lack of experience with similar applications. However, positive or negative feedback from the testers can be a deal-breaker when it comes to the release of an app. 

• Performance test - usually refers to the process through which the speed, responsiveness, and stability of an app or network can be established under a particular workload. At Tester Work, it is not very common to meet this testing method, but it’s always good to keep an eye and report issues that might relate to the general performance of a product. Does the loading take too much time? Does the app crash if tapping accidentally multiple times on a certain button? Report it!

• Regression test - it allows testers to re-verify if the old issues which were claimed as fixed are still reproducible or completely eliminated. It also helps detect possible bugs that appear as a result of the new fixes.

Our test cycles usually involve a mixture of multiple test techniques, but more important than anything else is, to always thoroughly check the test specs. 

This document is always included in the email sent by the test manager and presents indispensable details, such as test prerequisites, description of the app in test, what to test, expected behaviors, link to download the app, bug reporting instructions, helpful guides, and general guides.