Related Content
Merging New Codeless Test Automation with Your Existing Code-Based Test Scripts Adopting a codeless solution can be an amazing boost to quality, productivity, and tester career growth, but in most organizations, such test suites will have to be merged into existing code-based test scripts. To succeed, developers, testers, and management all should consider the differences between the two options. |
||
4 Reasons Your Company Should Hold a Developer Hackathon Hackathons, where developers meet up to do some collaborative programming, are a great venue for problem-solving and creativity. They give employees the potential to get ideas out there that could pay off big, work the bugs out of new technology, and increase morale—and, best of all, they can be held anywhere. |
||
Girl Scout Cookie Sales Help Fund STEM Badges, Including Cybersecurity and Programming It's officially Girl Scout cookie season, and that means you’re doing a good thing when you buy those boxes of cookies. The Girl Scouts offer science- and technology-related badges and journeys to introduce girls to computer science, robotics, mechanical engineering, space exploration, and cybersecurity. |
||
Solo Programming, Pairing, and Mobbing: Which Is Right for You? Programming often is considered an individual pursuit, but there are other options gaining popularity: pairing, where you work with another developer or tester, and mobbing, where the entire team works on one thing at a time. Each is effective for certain kinds of challenges. How much collaboration is right for you? |
||
Code Katas for Testers A kata is a small programming task you build a solution to. The point is to develop programming skill through familiarity with programming patterns, which is a useful practice for testers today. You’ll learn about software development, testing, continuous integration, exploration—and even how to be a better person. |
||
Mob Programming: Working Well Together Mob programming is a whole-team approach to creating software where everyone works together on the same thing at the same computer. It's not a bunch of people watching one person write code, but rather everyone thinking, discussing, designing, and collaborating. Sound crazy? Here's how it improves the quality of code. |
||
Testing Your DevOps Is Just as Important as Testing Your Software Many DevOps engineers fail to test their automation code in the same way they test the software they deploy. It's crucial for software to have tests, and this should apply to infrastructure-as-code software too, if we plan to change and improve this code with no worries about breaking automation in our DevOps pipeline. |
||
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. |