As the Agile environment has efficient principles that allow quick responses to changes and the ability to deal with uncertainty, exploratory testing may seem like a perfect match for such projects. However, this is only partially true. In reality, diverse reasons impede its usage in Agile projects, and companies should take them into account before designing QA strategies.
Static code analysis tools offer a range of benefits for software testing. By identifying potential issues early on in the development process, these tools can help improve the quality and reliability of software, the codebase’s maintainability, and software security by identifying potential vulnerabilities and security issues.
Protractor has been a popular choice for writing end-to-end (E2E) browser tests over the past decade. However, Protractor is being removed from the Angular project as of Angular 15 due to a loss of dedicated developers and the rise of better testing frameworks. Based on this state of affairs, what should developers working with Protractor do, and what tool choices do developers have going forward?
Whether to use Cucumber and BDD (Behavior Driven Development) is an old topic and a lot has been shared regarding this already. However I believe many times it’s just the high level technical reasons that make it to the forefront of the argument on how effective it is, and I want to address the topic from a holistic point of view and not just technical.
Migrating an organization to continuous integration requires adoption new processes, tools, and automation. DevOps relies on dramatic culture change to encourage total transparency and collaboration among all project stakeholders.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
Aprajita Mathur, bioinformatics software test manager at Guardant Health, discusses how to develop yourself and why it's so important to take the time to do so. She explains that your personal life will always be more significant than any work you need to get done, and she gives strategies for how to talk with your manager as well as your team when you are feeling overworked and need a break. Aprajita believes if you are self-aware and have open communication, then having these conversations will be easier and you can focus on yourself.
In this interview, Michael Faulise, the founder and managing partner at tap|QA, explains how the move toward DevOps and away from release management is giving control back to developers, then details why major companies often need partners to leverage CI, CD, and other modern techniques.
In this interview, Hans Buwalda, the CTO at LogiGear, explains how software developers have the mindset of creation while software testers are more concerned with how things might be destroyed. He details why testers don’t always need to code and why UI and API automation matters.
State Farm adopted an innovative approach to a common problem many organizations face with agile transformation: How do you influence, nurture, and support a whole scale culture of agility? How do you move from doing agile to being agile?
Behavior-driven development has been a buzzworthy term in the testing and development community for several years. At first glance, the elements of BDD seem simple: testing scenarios, living documentation, automation, and reports.
y now you have probably heard that there should be a healthy tension between the product and engineering teams. The key word there is "healthy"—when this relationship is unhealthy, silos tend to form, ideas may be thrown over the wall, and a lack of ownership can develop.
Kubernetes is one of the fastest growing open source projects in history, and it's taking the DevOps world by storm. With so many resources being poured into this technology, it would be nice if there were some benefits for testing.