Related Content
 |
Pros and Cons of Codeless Test Automation To create automated tests for software applications, testers have historically needed to be able to code in programming languages. Codeless testing eliminates the need for scripting from scratch every time, but in addition to its advantages, there are also some drawbacks. Is codeless automation right for your team? |
|
 |
2 Ways to Get Better at Test Automation Many people in testing roles want to grow their skills and learn to build some tests with code. But no matter how well you test, automation is programming work. If you want to get better at automation, your best bet is to get into a role where you are dealing with code. Here are two ways you can break in and learn. |
|
 |
Shaking Up Software Testing with AI: A Slack Takeover with Tariq King Thought leaders from the software community are taking over the TechWell Hub to answer questions and engage in conversations. Tariq King, founder and CEO of Selftest IO, hosted this Slack takeover and discussed all things AI, including using it with legacy systems, how it affects test strategy, and boosting your tests. |
|
 |
Scrum Roles, Goals, and You The Scrum Guide specifies that there are three roles: product owner, developer, and ScrumMaster. It’s essential that a Scrum team have each of these roles to help it work well. But depending on how you implement the roles, you may end up hurting rather than helping your Scrum process. Focus on goals, not job titles. |
|
 |
Testing Is Insurance, Not Assurance The Iowa Democratic Party used a mobile app to pull results from statewide precincts for the Iowa caucus. But the app was not properly tested or deployed, and it turned into a high-profile tech disaster. When deadlines loom, release testing is often what gets cut, but this situation shows why it's a crucial activity. |
|
 |
Why You Should Treat Tests as Products There's a case for treating some of your tests as products—project deliverables in their own right, created as a business investment. "Productizing" tests can show their value to management, but more importantly, it can help them contribute more effectively to the development lifecycle. Here are four steps to consider. |
|
 |
Does Agile Have Too Many Meetings? Because agile favors lots of short meetings, it may seem like they take up a lot more time. But when you compare it to time spent meeting in the pre-agile days, it's usually actually less. However, this doesn’t mean all meetings you attend are useful. Here are a few tips for deciding if all your meetings are necessary. |
|
 |
One-on-Ones: A Framework for Feedback Regular one-on-one meetings between a manager and employee are a forum to provide safe, timely feedback. They can be short or longer, but you should discuss successes, challenges, and how to improve. Having a framework for the conversation helps you make sure that the meetings don’t routinely become chat sessions. |
