Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesSoftware testing opinions that sound unpopular are often arguments against applying a familiar practice everywhere. A 2023 collection from Agile Testing Days gathered views from community members on agile testing; it is a set of practitioner opinions, not proof that any one approach works across all teams. Its useful question is not whether a practice is always right or wrong, but what risk it addresses, what information it produces, and what it costs to maintain.
What these opinions can—and cannot—tell you
Agile Testing Days asked community members for “what are some unpopular agile software testing opinions that they stand by.” The resulting collection includes contrasting positions on team responsibility, regression testing, automation, accessibility, test-driven development (TDD), and test cases. It does not establish how common or unpopular those views are, nor does it compare practices in controlled conditions.
That distinction matters: a practitioner’s argument can be a useful prompt without being a universal prescription. Eric Proegler’s framing captures the risk of treating advice as context-free: “There are no best practices or answers that apply to every context…Instructions that are context-oblivious or context-imperial are potentially harmful.” Agile Testing Days’ collection is best read as a set of questions teams can test against their own work.
Testing can be shared across the team
One view in the collection is that anyone on a team can test, and that a teammate’s unwillingness to do so can turn testing into a bottleneck. The related challenge is that even a dedicated tester need not personally test every feature. This is an argument for shared responsibility, not for eliminating specialist testing skills or leaving risk ownership vague.
Free tools Windows power users keep installed
One-click scans. No signup required.
When the argument is persuasive
Shared testing can help when developers, product staff, and testers can contribute at different points in delivery and surface issues before a handoff. It may also reduce queues that arise when all testing work is assigned to one person or role.
What to decide explicitly
- Who is accountable for identifying and prioritizing risks in each change?
- Which checks can contributors across the team perform, and which need specialist knowledge?
- How will findings be recorded, investigated, and resolved rather than assumed to be someone else’s responsibility?
Sharing tasks does not by itself ensure adequate coverage. Teams still need to make clear who can investigate complex failures and who has authority to delay a release when a material risk remains.
More testing is not automatically better
João Proença’s opinion in the collection is blunt: “Sometimes a lot of testing is exactly what you don’t need.” That is a warning about volume as a poor proxy for value, not a case against testing. A large suite may produce slow feedback or require maintenance that crowds out work with greater risk-reduction value.
Joanna Denni’s cited view questions excessive regression effort and automation when jobs center on generating large volumes of tests and acting as release gatekeepers. It does not demonstrate that regression testing is generally unnecessary. The practical question is whether a given check is still detecting a meaningful failure mode at a cost the team accepts.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Assess a test by its contribution
- Risk: What failure could this check detect, and what would the consequence be if it escaped?
- Feedback: Does the result arrive soon enough and explain enough to guide a decision?
- Maintenance: How often does the check need repair or updating, and what work does that displace?
- Coverage: Which users, platforms, or accessibility needs does it represent or miss?
- Action: Does someone with the skills and authority to respond own the result?
A check with little diagnostic value, substantial upkeep, and no clear risk to cover may be a candidate for revision or removal. A slow or costly check may still be warranted if it protects against a serious failure that faster checks cannot detect.
Accessibility testing is a must, not a nice-to-have
Eduarda Loureiro’s position in the collection is that accessibility testing is a must rather than a good-to-have. Treat that as an attributed practitioner view. The collection alone does not establish legal requirements, a particular standard, or a complete accessibility-testing method.
For a team, the claim is a prompt to consider whether its testing approach notices barriers experienced by people with different access needs—not merely whether the interface works for the most common path the team happens to exercise. Decide what accessibility risks are relevant to the product and how the team will investigate them; do not infer that one automated check or one round of testing settles the question.
Test-driven development and exploratory testing need not compete
Lisa Crispin argues that teams should learn TDD. The collection also notes concern that exploratory testing can be overshadowed by TDD and behavior-driven development (BDD). These are not necessarily opposing camps: a team can use tests written before implementation to guide some development while also investigating behavior that predefined checks do not cover.
The collection attributes a numerical claim about bug prevention to Dave Farley, but does not provide a primary source that verifies it. The figure should not be treated as an established statistic. The stronger practical takeaway is to ask what kind of feedback a technique provides and what kinds of discovery it might leave out.
Rank #4
Questions for choosing a balance
- Which expected behaviors benefit from fast, repeatable checks while code is changing?
- Where could unexpected interactions, usability problems, or unanticipated states escape scripted checks?
- Does the team have time and skill for both structured checks and open-ended investigation?
Traditional test cases are not the only route to quality
Butch Mayhew’s opinion challenges the idea that executing traditional test cases is required to release high-quality software. That claim questions one method, not the value of planning or recording testing. Test cases can be useful for repeatability, communication, and regression checks; they are not the only way to investigate a product or gather evidence about quality.
Rather than debating whether a team “has test cases,” ask whether its methods expose the relevant failure modes, produce findings people can act on, and preserve the knowledge that needs to be repeated. A scripted case may be appropriate for a stable, important behavior; a less scripted investigation may be more informative where the behavior or risk is uncertain.
What a separate survey does—and does not—add
An indexed abstract for a separate study reports responses from 72 practitioners in eight countries and says test management and test automation were the most challenging activities for those respondents. This is a result about that study’s respondents, not an industry-wide ranking or evidence that either activity should be abandoned. The abstract record’s study details are incomplete, so the result should be treated cautiously rather than used to quantify how testers broadly feel.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Best Value
A practical way to evaluate a testing opinion
- Name the claim. State the practice being challenged—for example, assigning all testing to a dedicated tester or automating every regression check.
- Identify the risk. Describe the failure the practice is meant to prevent and the likely consequence of missing it.
- Look at the information and cost. Consider feedback speed and usefulness alongside setup, maintenance, and delay.
- Check who and what is covered. Include user needs, platforms, specialist skills, and clear ownership of decisions.
- Try a bounded change. If the evidence supports an adjustment, make it small enough to observe its effects and revisit it if risk or costs change.
This approach avoids turning a provocative opinion into a new rule. It makes the argument answerable in the team’s own context.
Capture a page as part of investigating a testing issue
When an issue depends on how a page appeared at a particular point in an investigation, a screenshot can preserve that visual state for review. ScreenshotNeo is a website screenshot API and MCP server for developers; it is relevant when teams want to capture pages programmatically or through an AI agent. This is a practical capture option, not a substitute for deciding what to test or assessing accessibility.
Or skip the browser setup
One GET request can return a screenshot. Replace the target URL and provide your API key:
Quick Recap
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before capture; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots per month with no card, and paid plans start at $5 for 3,000.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Sign up for ScreenshotNeo’s free plan.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
