Agile Roundup: Feeling a Little Testy
Agile Roundup: Feeling a Little Testy
In this month's edition, we look at Agile testing practices, how they're evolving, and how testing can keep up. Read on!
Join the DZone community and get the full member experience.Join For Free
In this month's Agile Roundup, we explore the wide, wonderful world of testing! So read on to explore topics like how to write tests, changes to the manual testing field, and coding smells in unit tests, and have your assumptions tested! Get it?! Because of the testing thing... Anyway, let's get to it!
And, as a quick side note, if you're interested in writing for DZone, but don't have a topic in mind, come check out our Bounty Board, where you can win prizes for providing great content!
Testing, Testing... 1, 2...
7 Popular Unit Test Naming Conventions by Ajitesh Kumar. Do you use the most popular, well-known naming conventions when writing your unit tests, or do you use the naming conventions that sit by themselves in the corner because they smell bad? Find out in this article!
Writing Good Tests by David Bernstein. When it comes to Agile methodologies and code quality, few, if any, say it better than Mr. Berstein. So, I'll let him do the talking: "Good tests are extremely valuable because they help you build out behaviors in ways that make sense and they support you in refactoring your code later. But in order for tests to have these amazing benefits and more they must be good tests. They must be unique, at the right level of abstraction, based on acceptance criteria, and be implementation independent."
Changes Manual Testers Must Embrace by Monica Paul. We look at things that manual testing professionals can do to stay ahead in their field as software testing becomes increasingly automated.
Unit Testing Smells: What Are Your Tests Telling You? by Erik Dietrich. A look at some the ways that testing can go wrong, and 'smells' that programmers, accidentally, implement, in their code. If your test code smells, consider this your testing deodorant.
Today's Approach to Testing Has No Future, Part 1 by Leszek Zielinski. You can almost hear the sound of Sarah McLachlan playing in the background, while images of poor, abandoned testing solutions fly past the screen. A quality assurance engineer explains why some in the industry continue to ignore the best testing solutions, and why this approach is untenable in the long term.
Ace the Testing Test
Test Driven Development Is Not a Quality Assurance Technique by Mark Levison. Amen, brother! Test Driven Development isn't a way to check the quality of code after it's been written, it's a way to ensure the quality of code while it's being written.
When to Stop Testing by Dave Nicolette. Using the terms testing and checking interchangeably is something that most developers are probably guilty of. If this guilt is weighing on your conscience, keeping you up late into the night, read on to understand the difference. And, even if it's not, you should still read the article.
Engineering Hight Quality Through Agile Testing Practices by Dan Radigan. A look at why shifting testing practices left in an Agile development environment is so important to the end product's quality. Maybe Beyoncé can do a remix of Irreplaceable, "Every test I run, shift it to the left." Or, maybe not...
DZone Testing Publications
DZone's Guide to Automated Testing: Improving Application Speed and Quality featuring articles by Jim Holmes, Carlo Cadet, Maciej Gryka, Mirco Hering, Niklas Wuensche, Tamas Cser, Slaven Slugic, Soumyajit Basu, and Tom Smith. Automated testing has many exciting benefits, like decreasing time to market, improving software quality, and incentivizing developers to build applications that will pass tests the first time around. The 2017 Guide to Automated Testing covers what code can or should be automated and tutorials to get you started. Learn more about mobile testing in Kotlin, go beyond what Selenium provides for web application testing, and take a deep dive into trends such as Behavioral-Driven Development and Visual Regression.
DZone Refcard: Continuous Testing 101 by Christopher Springstead. There are many misconceptions as to what Continuous Testing is. Is it the same thing as Continuous Delivery? It’s probably a QA-led activity, right? You’re getting warmer. These concepts are certainly connected. Let’s push the misconceptions aside and learn exactly what Continuous Testing is, the 10 key elements of Continuous Testing methodology, and the benefits of utilizing this concept.
Find Your Next Great Agile Gig!
The ideal candidate will have 5+ years' experience working on Java development projects with UI technologies, and a minimum of one year worth of experience designing large scale software systems. Other required skills include: experience with web technologies; knowledge of Angular/KnockoutJS/Bootstrap; expertise in Object-Oriented Analysis and Design Patterns; strong knowledge of data structures and algorithms; and scripting experience using DOS, Unix Shell, Perl, etc. This role is located in our Agile Ops team and will work collaboratively within an Agile Team to write high quality, testable code that meets the Definition of Done.
The ideal candidate will have 3+ years' experience in software development, with knowledge of ROS, Player Project, JAUS(SAE AS-4), or other robotic standards, and developing software for robotic perception, sensor fusion, and decision making. Additionally, experience building cross-platform mobile applications and secure web applications is a plus.
Opinions expressed by DZone contributors are their own.