Related Content
 |
Elevate Code Quality by Integrating Testing and Development Pair programming generally involves two programmers working on a single change from start to finish. You can augment this pattern by adding a test specialist, so you can test-drive feature changes first and the tester can ask questions and guide test and code design. What you get is quality built in from the start. |
|
 |
Artificial Intelligence and Health Care: Predicting Patient Deterioration As part of a medical research partnership with the US Department of Veterans Affairs, the team of scientists and engineers at DeepMind, the artificial intelligence group at Alphabet (Google’s parent company), will work on the global issue of patient deterioration during hospital care. |
|
 |
Do Testers Really Need to Learn How to Code? Because automation, AI, and agile have changed how we test software, the thought is that testers need to understand a certain amount of coding so that they can make themselves more well-rounded and better able to adapt within a software project. But there are other things testers can focus on before learning to code. |
|
 |
4 Key Factors Driving Digital Transformation There are so many strong reasons why digital transformation has become big, but many organizations are missing a major opportunity by simply running digital projects instead of fully transforming the organization itself—similar to doing some agile things without actually committing to being agile. |
|
 |
Testing in a Pair Programming Environment If a development team does pair programming, where does testing fit in? You don't have to wait until the programming is done—testers can be part of the whole process, from code design to reviewing changes to production. Pair programming plus a good automation strategy mean quality is built in throughout development. |
|
 |
What's in the Winter 2018 Issue of Better Software Magazine As Better Software magazine continues to publish articles that propel our industry forward with great tips and techniques, TechWell sees the future focused on continuous processes. Three of this issue's feature articles will help you improve how enterprise software is planned, developed, validated, and released. |
|
 |
Interface Grief: Is It Agile, or Just Bad Software Engineering? There are people who will use "being agile" to justify software engineering practices that could be perceived as lazy or even bad. The specifications are going to change, they say, so it would be a waste to engineer more to begin with than the minimum viable product. What's expediency and what's just poor practice? |
|
 |
Why DevTestOps Might Be the Next Big Buzzword The hope with any new concept is that it produces better results while removing certain tedious steps that might cause frustration along the way. While DevOps does change the way you test, you cannot forget that testing is still a major layer to your success. |
