Related Content
Testing the Requirements: A Guide to Requirements Analysis Everyone knows testing requirements is important, and everyone says they do it, but it seems like no one knows exactly how. The best way to solve this problem is to introduce a requirements analysis stage that has to be done before coding starts. No one knows a product as well as a tester who works with it every day! |
||
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. |
||
Data Means Nothing if You Don’t Know How to Use, Analyze, and Interpret It Simply having data stowed away and ready to use when needed is great and all, but if you don’t have a smart strategy for how to not only analyze and interpret it, but also put it to proper use, then you may end up creating a connected ecosystem without a real purpose. |
||
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. |
||
DevOps Isn’t a Fad, So You Need to Invest Now It’s easy to get wrapped up in the promise of ten-times greater production, shorter development times, smarter testing, and everything surrounding the fresh idea of the day, but when it comes to DevOps, there’s no longer a need for trepidation. DevOps is here to stay. |