Related Content
2 Ways to Know Your Work Is Actually Done Some people think a good indication that a piece of work is done is if it's been tested. But by whom, and how? Testing alone doesn’t specifically determine whether you are done—especially when we probably don’t mean the same thing when we all talk about testing. Here are two ways to know when your work is truly done. |
||
Trusting Your Data: Garbage In, Garbage Out Poor quality input will always produce faulty output. Improper validation of data input can affect more than just security; it can also affect your ability to make effective business decisions. Bad data can have impacts on how you make quantitative decisions or create reports, if you can’t trust the data you receive. |
||
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! |
||
Use Self-Evaluation to Stay on the Right Career Track Employer evaluations measure your performance against expected objectives, evaluate you against other employees, and aim to keep you relevant in your company. But it’s also a good idea to perform a self-examination in relationship to your place of employment, to ensure you stay attractive to potential future employers. |
||
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. |
||
Automation Face-Off: A Conversation with Michael Bolton, Isabel Evans, and Chris Loder Automation is a pressing topic. In a recent STARCANADA keynote session, industry experts Michael Bolton, Isabel Evans, and Chris Loder took to the conference stage to discuss some of the burning questions about automation from test professionals in the audience. Here’s a sample of their conversations. |