Posts

It's all About the Next Person Taking Over From You.

-
If there is one thing engineers and developers despise, is DOCUMENTATION! It takes away the joy and the pleasure we derive while building software. However, documenting your code is a Gift for Future Engineers and Developers. Writing clean code is essential, but even clean code can be puzzling without context. Documentation is not just for you; it is a lifeline for future engineers. It captures the why behind your work, making transitions and scalability smoother and preserving continuity in the long run. Clean code matters not just for good Code Quality, It goes beyond that. Even the best-structured code can leave future developers guessing about design choices and updates if there is no documentation to provide context. Imagine a new engineer taking over your project. They may find the code clean, yet the logic or the reason behind specific decisions may not be immediately clear. Having a backstory (Documentation) helps them understand not only what the code does, but why it w...
Post a Comment
Read more

5 Habits to Survive as a Tester - Richard Seidl

-
We live in an extraordinarily changing world. You see it every day, AI and other technologies are evolving rapidly. Today, I want to share some things I believe will be helpful for the future. These will help you build better relationships with your colleagues, advance your career or business, and make a greater impact as a software tester. I have been working with clients for over 25 years in the software testing field, testing countless software and working with many people. Based on my experience observing how testers and test managers perform their jobs and what they focus on, I’ve identified 5 key habits that make a good, resilient tester who can succeed in the future. When I work with clients through my mentoring program, they often ask, “Richie, what should I focus on? How can I grow? What areas should I pay attention to?” Today, I’m going to share with you the five key areas I recommend focusing on, areas I include in my “buffet” of recommendations for my clients. Let’s dive in...
Post a Comment
Read more

There Is No “Manual vs Automated Testing” Conflict - Cassandra H. Leung

-
I’m a little bit frustrated. Since Twitter died and I decided to start engaging on   LinkedIn   more, I keep seeing posts that perpetuate this idea of “manual” vs automated testing; us vs them.   There is no versus. Your civil war is manufactured. There’s room for everyone and we all want the same thing: good quality.   I’m frustrated by posts which pit people against one another; which disparage human testing; which claim automated checks bring less or no value;  which distract us from actually improving quality .   Testers are specialists. Automation is a tool. Specialists use tools. Not every tool is right for every job. A specialist knows which tools to use and when. What’s the problem here?   I specialize in exploratory testing. I’ve written some automation before and I’m actively working to improve those skills, not because I want to replace my exploration, but because I want to contribute more to making more room for it.   Think of making t...
Post a Comment
Read more

Why do I need a separate testing team if developers can test the product themselves?

-
Having a separate testing team is a beneficial way to ensure that the product is tested and validated from an unbiased point of view. Developers may be too close to the code of the product to provide an unbiased evaluation of it, and may not be completely objective about the quality of the product. A separate testing team, that is entirely independent from the development team, can provide a more accurate assessment of a product. This can result in a better and more reliable product that meets quality standards. While developers can and should test their code to ensure that it meets the expected functional and non-functional requirements, there are several reasons why having a separate testing team can be beneficial: Independent perspective and reduced bias: A software testing team can provide an independent perspective on the software being developed. Developers may be biased towards their own code and may not identify issues that are present. Therefore, having a separate team to...
Post a Comment
Read more

The True Purpose of Testing - Artem Zakharchenko

-
Image
Let me ask you a question: What are the automated tests for? Whether you’ve written some tests in the past or not, you’ve likely heard that tests can be useful. And I know you’ve also heard stories about tests that are more of a chore and nuisance than any help. Frankly, I believe both parties are right! But to understand why, I will first let you in on a little secret. No test is inherently useful just because it exists. A test becomes useful when it fulfills its purpose. So, what is that purpose exactly? As the name implies, automated tests are here to help us automate something. We take a particular state of our application, perform some actions, and check the resulting system to be what we expect. That’s what any test does, and yet some tests are more useful than others. There is precisely one thing that defines and controls that difference. The intention Just as every piece of code exists for a reason, every test exists to verify the intention behind that code. A paragraph is rend...
Post a Comment
Read more

EVERY TESTING NEEDS A HUMAN TOUCH: WHY AUTOMATION ALONE IS NOT ENOUGH

-
Automation testing has revolutionized the way we test software by enabling rapid execution of test cases, efficient bug detection, and improved overall product quality. In a rapidly changing tech ecosystem where speed, efficiency, and accuracy are paramount in software development, adoption of new automation tools and frameworks have has increased significantly in recent years. However, despite the need to automate testing for faster deployment, the fact remains that every software testing endeavor needs a human touch. To better understand the importance of human element in every software testing, there is equally a need to understand the role of using automation tools in software testing especially in a large-scale software development. Understanding the Role of Automation for testing Automation in software testing refers to the use of specialized tools and scripts to execute predefined test cases, perform repetitive tasks, and validate software functionality automatically. By adoptin...
Post a Comment
Read more

WHAT ARE THE ROLES OF A SOFTWARE TEST MANAGER

-
  In our previous post, we discussed the roles and responsibilities of a Software Test Analyst. As mentioned, the Analyst supports the Manager in the testing activities and processes. Now we are going to discuss the role of a Software Test Manager. A Software Test Manager is responsible for overseeing and managing the entire testing process within an organization or a specific project. They have wider range of responsibilities to make the testing process as seamless as possible.  A Software Test Manger assumes the following roles in a testing project/teams:   1. Test Strategy and Planning: Every project starts with implementation strategy and planning. This determines the success of a project. Test Managers develop a comprehensive test strategy and test plan for each project or product. This includes defining the scope of testing, objectives, timelines, resource allocation, and risk assessment.   2. Team Management: They are responsible in the recruitment, ...
Post a Comment
Read more