“Several core practices used by agile teams relate to testing.”
Programmers using TDD, code integration tests being written contribute to a successful project.
“Agile Testing just doesn’t mean testing on an agile project.”
Some testing approaches like exploratory testing are inherently agile, whether done in an agile project or not.
Testers are integral members of the customer team as well as development team
The best part of this chapter is Lisa and Janet’s wonderful stories on beginning with their first agile projects, and a realization by Janet’s co-worker, a developer in a team following XP on how they saw Janet’s contribution to the project.
“Testers don’t sit & wait for work; they get up and look for ways to contribute throughout the development cycle and beyond.”
Traditional vs Agile Testing
In Traditional approach – “Testing gets “squished” because coding takes longer than expected, and because teams get into a code-and-fix cycle at the end.
In Agile – “As an agile team member, you will need to be adaptive to the team’s needs
“Participants, tests, and tools need to be adaptive.”
“An Agile team is a wonderful place to be a tester”
The Whole-Team Approach –
“Everyone on an agile team gets “test-infected.”
“An agile team must possess all the skills needed to produce quality code that delivers the features required by the organization.”
“The whole team approach involves constant collaboration”
“On an agile team, anyone can ask for and receive help”
“The fact is, it’s all about quality – and if it’s not, we question whether it’s really an ‘agile’ team.”
I used to love books, reading was a fun and satisfying hobby for the introverted teen I was. But lately I may have gotten away from it for known and unknown reasons. I want to pursue the passion again and hold myself accountable too. So, this year I am starting a ‘Read Along’ series on my blog.
I have learnt agile testing by doing it, learning it hands-on, training & running courses on agile testing for professionals. I wanted to enhance my knowledge by reading the professional work by these awesome ladies.
So, I will be reading the book and will post about learnings, things to remember & quotable quotes from each chapter as I progress. This is to hold myself accountable, as well as to help people looking for good reads or learnings. Hope this helps you. Have you read this book? Do share your thoughts & learnings too!
Learning is an ongoing process, and hopefully a lifelong one. Being a professional in any field requires you to constantly update your knowledge and continue to learn.
Software testing is a very in-demand role, so many people aspire to get into this line of work — but they may not know where to begin.
If you are fresh out of college or looking to switch careers, even if you are not from a computing or engineering background at all, you can jump-start your career in testing. In my article published at TestRail blog, I have given some tips and advice on how to become a self-taught software tester this year.
Books provide a world of knowledge, and despite shifting trends, books can never be outdated, as older ideas can give you a foundation for new information. Reading a book allows you to delve deeper into a topic of your choice at your own pace.
Begin by searching for books on software testing, quality assurance practices, and industry leaders.
Then seek books that can help you start applying the knowledge.
If picking up a physical book is not your cup of tea, read online — there are many great portals with awesome content, articles, and ideas.
Diversify Your Knowledge
Software testing is not a singular skill; it requires a number of skills, both technical and non-technical. When beginning your quest to learn about software testing, delve into various areas of the domain and look for what interests you the most.
Welcome to a place where you can find the best content related to software testing, test automation and agile space.
Difference Between Human Testing & Test Automation
Human Testing is a craft that is more than executing a bunch of tests, performing clicks and actions. A tester has a unique understanding of the system and ways to critique it. Over time, the tester develops a deeper comprehension of the application and its intricacies, integrations, weak points, and history. This makes them the best judge to find out the failure points of the system and comment on its health.
While automated checks can help in determining problems in what we know (and have scripted as checks), it may not help as much in the risk areas of what we do not know about the product. That requires exploration, creativity, intuition and domain knowledge. This is the human aspect of testing.
Testers find defects and raise awareness about quality. What happens after the bugs are found can be any tester’s guess, though. Bugs may get delayed, postponed, go unnoticed or linger on due to lack of information.
In my article for Ranorex blog, I talk about how Testers need to champion the cause of their bugs in order to avoid unneeded delays in fixing defects that are important. At the same time, testers should maintain a distance to make it an impersonal and impartial experience. Testers need to master the art of bug advocacy!
Why is advocacy important?
Advocacy is basically pleading the case for a bug to be fixed. The testers who find the bugs are the ones who need to advocate for their bugs. It is important that they take a stand and voice their opinions.
Some bugs may not be deemed important from a business perspective, as they seem too small. But in reality, they may be blocking an important feature for a particular user group. On the other hand, some bugs may seem more critical than they truly are, and while fixing them may be important, it may not be the highest of priority.
Whatever the case, testers must aim to present the facts and data in such a way that decision-makers are able to make well-informed resolutions about the issue.
Communication is key
Advocating for anything is not a one-way street. It takes discussion, debate and reaching a consensus on key points to make a collective decision. This is where testers’ communication skill plays a key role. Testers need to have good communication, both verbal and written.
That said, this article will help you identify burnout symptoms so you can understand this syndrome better for yourself and for those around you who might be experiencing it too.
The following are some warning signs of burnout:
Irritability and indifference
Tech Republic notes in an article on burnout warning signs that being irritable and indifferent are telltale signs of burnout. Granted, getting irritated is a normal reaction — but if it happens more than usual or if you end up snapping at someone for the smallest reason, you’re likely burned out. The same holds true when both your attention to detail and job interest wane. This increasing detachment is one of the three dimensions of burnout, according to the WHO.
It’s normal to feel tired at the end of your work shift, but if you feel drained just hours (or even minutes) after starting work, then you’re probably burned out. This energy depletion is yet another dimension of burnout, and it can be exacerbated by the long hours expected of you.
Testing concepts and techniques can be learned. But having a knack for testing is different. What makes someone a born tester? What are some personality traits and skills that can make a person innately good at this profession?
In my latest article published at https://blog.gurock.com/natural-traits-great-tester/ , I have described four traits that belong to people who naturally make great testers. Developing these traits can help you in your testing career, and if you are a manager, these are the traits to seek when looking to hire new testers for your team!