On a bright day at an IT firm, two evaluators are conversing in front of the snack dispenser –
Evaluator 1: this job is deplorable. I spend my entire day running the same test suites that I did the previous day, and most of them still have failures. The project manager is displeased with me because the test suites are not passing and I’m uncertain about what to do next.
Recommended IPTV Service Providers
- IPTVGREAT – Rating 4.8/5 ( 600+ Reviews )
- IPTVRESALE – Rating 5/5 ( 200+ Reviews )
- IPTVGANG – Rating 4.7/5 ( 1200+ Reviews )
- IPTVUNLOCK – Rating 5/5 ( 65 Reviews )
- IPTVFOLLOW -Rating 5/5 ( 48 Reviews )
- IPTVTOPS – Rating 5/5 ( 43 Reviews )
Evaluator 2: I concur. I encounter the same issue. There seems to be no innovation in the work I do. I’m expected to write test suites every day, and whenever I propose fresh notions, they are turned down with varying pretexts.
Evaluator 1: I am on the hunt for a fresh role that allows me to grow and explore… … ….
Evaluator 2: Inform me when you’ve applied somewhere, as I’m eager for new prospects as well.
What conclusions can you draw from the above conversation?
- Both evaluators are looking for new employment
- Both evaluators are worn out from their current tasks
- Both evaluators find their current work lackluster
- Both evaluators are convinced they’ll find something intriguing in a fresh role
Well, the reality is – there’s no such thing as a boring job, especially NOT in software testing. It’s the individual’s viewpoint that makes it appear so. I understand that there may be numerous counter-arguments.
Let me now further illustrate my point –
As an evaluator, your assignment is to test the login page of an application, which is intended to function across a range of platforms. It’s your duty to test it exhaustively.
- Do you believe the job is boring?
- Do you believe you’re not gaining new insights?
- Do you ascertain there’s nothing to uncover?
Consider the following situations –
- What transpires if the user provides login details and then closes the browser? Are the credentials retained?
- What transpires if the same user attempts to log in from different platforms simultaneously?
- What if the user has to wait a couple of minutes before being directed to the homepage after submitting their correct credentials?
- What if the user provides accurate login details, but the database server doesn’t respond? What would the user perceive?
- What happens if the user enters accurate credentials and leaves the page unattended for 30 minutes without hitting OK or Submit?
- What happens if the user enters accurate credentials and hits the OK or Submit button 10 times consecutively?
- What happens if the user enters correct credentials and then clicks on “Forgot Password”?
- What happens if the user modifies the login page’s URL by appending an SQL injection query?
- Would the knowledge about how the login page operates in other apps make a difference?
- Would staying informed about UX (User Experience) enhancements in the industry have any impact?
Are the above aspects intriguing? Certainly yes. Nevertheless, they may appear mundane when you need to execute them for all compatible platforms.
Let’s strategize here.
Carry out all the tests for one platform. Spot critical issues and corroborate their existence on the other two platforms. If they persist, there’s no need for additional testing, and the build can be dismissed.
Triggers for redundancy in the role of a software evaluator:
If I were tasked with listing the causes for redundancy in the evaluator’s role, I’d cite the following points:
- Perhaps the evaluator is unable to think creatively
- Perhaps the evaluator is too lethargic to carry out the same test suites repeatedly
- Maybe the evaluator is disinterested in acquiring newer skills
- Perhaps the evaluator doesn’t know how to employ their newly learned skills
- Perhaps the evaluator lacks zeal for testing
- Maybe the evaluator grapples with self-motivation
- Perhaps the evaluator feels remorse about not identifying bugs
- Maybe the evaluator is uncertain about practical testing, and only familiar with theoretical knowledge
- Maybe the evaluator simply doesn’t wish to reason beyond scripted test suites
- Perhaps the evaluator is not permitted to venture due to a hefty workload or restricted access
- It’s possible the evaluator feels strained in terms of deadlines and expected results
- Perhaps the evaluator has lost enthusiasm for their profession
- Maybe the evaluator hasn’t had a break in a while
Ways to tackle redundancy as a software evaluator:
Discovering the underlying cause of redundancy and addressing it is the remedy.
Recognize that if you’re finding redundancy in the most dynamic field, you must focus on self-improvement. How can you achieve this? Well, there are numerous ways –
#1) Participate in discussions: Constructive discussions can lead to enlightenment for both you and your peers.
As an evaluator, engaging in dialogue about scenarios, outcomes, application behavior, and bug resolutions has invariably aided me in understanding and taking into account factors that I may have overlooked. I’m confident most evaluators would endorse this.
Also, consider reading =>
What’s the Optimal Approach to Cultivating Healthy Developer-QA Relationships? and
How Crucial is Communication Between Evaluators and Developers?
#2) Discover and grasp: Software testing is primarily about conceptualizing, as I’ve iterated several times. Anyone can run predefined test suites, but devising different test scenarios necessitates constant learning from other applications, team members, cohorts, and the industry at large.
When you condition yourself to scrutinize everything with a “testers” eye, you evolve into a genuine evaluator who can make a positive impact.
#3) Study and acquire knowledge: The software industry is perpetually transforming. Fresh technologies, challenges, and experiences come to light every day. As an evaluator, it’s pivotal to continually learn, stay adept with what you already know and unearth what’s unknown to you.
Put what you learn into practice and strive for advancement every day. Experiment with this STH resource to gain access to all the resources you’ll ever require.
#4) Self-inspiration: Self-inspiration is crucial for software testing. Often, people resent you or rebuff your suggestions when you find flaws in their work. It takes time to train oneself to perceive these negatives as positives and spur yourself each time.
#5) Lastly, you must read this => 16 Actions to Take When Testing Becomes Tedious
Hence, the next time you start feeling as though your role as an evaluator is monotonous, take comfort in the fact that we’re fortunate enough to have the chance to think creatively, enact ideas, scrutinize things, and eventually decide if a particular thing is suitable for usage or not… Isn’t that incredibly satisfying? Absolutely, it is!!!
Author: This positive perspective on navigating the evaluators’ journey has been penned down by Bhumika M., an integral part of the STH team. She carries an experience of over 10 years in the field of software testing.
Happy evaluating, readers… Give yourselves a pat on the back 🙂