24 / 07 / 31
OTP#7: Tools, Libraries, Frameworks & A Mobile Testing Heuristic
Outside The Parameters (OTP) is a human-authored micro-correspondence focused on sharing Software Testing stuff, published every other day.
Hello Tribe,
No doubt, it's been a while since we synced. It's one of those times when the work of Software Testing sucks up all of your time and forces every other thing to be at a standstill.
We are looking at some options to keep the letters rolling in to stem the effect of periods when work comes calling.
On Tools, Libraries and Frameworks
There's usually a juxtaposition of this trio. We stumbled on what we believe is a good attempt at defining the distinction between these terms.
According to Arek Frankowski :
Test tools are specialized applications designed to perform specific testing tasks, often catering to aspects of the testing process, such as API or load testing.
Examples of Tools: Postman, SoapUI, Loadrunner, etc.
Test libraries are collections of pre-written code that provide functionality to support testing activities. They simplify the process of writing test scripts by offering reusable functions and methods. These test scripts must then be executed within the context of the programming language in which they are written.
Examples of Libraries: AssertJ, RestAssured, Selenium, etc.
Test frameworks are comprehensive solutions that provide the structure and guidelines for organizing and executing tests. They integrate various tools and libraries to create a cohesive testing environment. Unlike test libraries, frameworks provide a running method for managing test execution.
Examples of Frameworks: Robot Framework, CenterTest, etc.
_Extras_:
_Tools_ are highly effective for specialized testing tasks but may have limitations for broader testing needs.
_Libraries_ enable testers to write concise and readable test scripts, handling common testing tasks and reducing the amount of boilerplate code.
_Frameworks_ deliver rules and tools used for building test cases and are designed to help engineering functions work more efficiently.
A Mobile Testing Heuristic You Should Know
In our last issue (OTP #6 ), we introduced 'Heuristics in Testing' and shared an example of its application in testing the "usability of errors" (FAILURE).
Today, we will be looking at an application of heuristics in mobile testing. This particular heuristic is a mnemonic that can be used to generate test cases for mobile app testing.
Jonathan Kohl formulated I SLICED UP FUN in 2010, and it means:
I = Inputs
S = Store
L = Location
I = Interactions/Interruptions
C = Communication
E = Ergonomics
D = Data
U = Usability
P = Platform
F = Function
U = User Scenarios
N = Network
If you click on this hyperlink → I SLICED UP FUN above, you will be directed to Jonathan's PDF which contains a detailed breakdown of the heuristic/mnemonic.
We will break this down in a future issue, but for now, we'd like to keep this issue small and concise.
Please help us know how our emails make you feel, using the poll at the bottom. This will help up improve and make OTP better - for you.
Thanks for reading.
Please help share OTP with your friends, co-workers and ex-colleagues.
Click to share via Twitter , LinkedIn , or Facebook , or use the Share function in the Comments area.
If visited this post or website directly, you can get your OTP your sub here .