Related Content
Great Testing Comes from Great Questions Testing is all about gathering information, and the most direct way to gather information is by asking questions. The more questions we ask (tests we perform), the more answers we receive (information we gain). But some questions are harder than others and require more human involvement. Let automation handle the easy! |
||
A Software Testing Primer When development teams are pressed for time or budget, testing is often the first activity squeezed out. But testing will actually save you money in the long run. This story gives the basics of why it's crucial to test early and often, the types of testing you should perform, and how to get proactive against bugs. |
||
Testers Must Use Team Connections to Enable Quality The quality team has the greatest reach in its visibility and ability to connect with all other engineering and non-engineering teams. For a tester to realize their fullest potential, they need to acknowledge and leverage this reach by communicating and collaborating with all other teams to create the best product. |
||
Security Testing and Assessing Risk: A Slack Takeover with Shachar Schiff Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Shachar Schiff, founder and principal consultant at BadTesting, hosted this Slack takeover and discussed assessing code coverage like a risk analyst, risk assessments outside security, and more. |
||
2 Ways to Standardize QA Practices Testing can get complicated when each project is using a completely different toolset, language, and reporting status, with different measurements and formats. Testing is a reaction to context and what we encounter, so how we test cannot be standardized. What we can standardize is the stuff that surrounds the testing. |
||
Getting Support for the Tests You Need Done It’s often hard for teams to get sufficient time and resources for the amount and quality of tests they think are needed. It’s like management wants testing done but at the same time doesn’t want to commit what’s needed to do it. If that's your case, look at the business side, rank priorities, and negotiate resources. |
||
Smart Testers Adopt Smart Automation As technology continues to evolve, questions around the role of quality also continue. Is manual testing still required? What should the role of automation be? Where are we heading with quality? Smart testers hoping to develop their careers will have to brush up on their exposure and expertise and embrace automation. |
||
A Simple Rule of Thumb for Unit Testing There's a simple rule for the minimum values testers should explore: “none, one, some”—or, how the software behaves if you send it nothing, one thing, or some set greater than one. It's not comprehensive, but it gives a good feel for how the feature works at the moment. Developers can also use this in unit testing. |