SmartBear Software, a prominent ALM and monitoring tool vendor acquired Eviware, creators of popular open source web services testing tools soapui and loadui, last week.
The recent release of Eclipse Indigo includes Jubula, an automated functional testing tool for Java and HTML applications. Tests are created via drag and drop of built-in test libraries, instead of application recording or test programming.
NativeDriver offers test automation for Android and iOS native applications. It implements the WebDriver API.
Machiel van der Bijl from the University of Twente in the Netherlands recently introduced a Model-based testing approach which is supposed to automate software testing.
Microsoft has unveiled at TechEd North America 2011 some of the new features coming in Visual Studio: more Agile tools for project planning and collecting stakeholder feedback, a connector for providing operations feedback to developers, plus architecture diagrams and unit testing for VC++.
Several members of the Agile community describe different styles for expressing user story tests and the testing of an entire theme.
Palladio Bench supports architects and developers in deriving quality of software estimations such as performance, reliability, maintainability and development costs from models. Its new version 3.2 is based on Eclipse 3.5 (Galileo) and adds several stabilizations and fixes, a reliability analysis, a new graphical editor and a new workflow engine, as well as a probe specification framework.
The latest version of Application Lifecycle Management (ALM) collaboration tool Tasktop supports task federation, cross-repository Agile planning, and new connectors to other ALM tools like HP Agile Accelerator and SmartBear CodeCollaborator. Tasktop team last week released version 2.0 of the software which also has integration with Hudson CI tool.
New groups, conferences and workshops promote the traditionally neglected tester role, spotlighting the skills, tools, and principles needed to be an excellent tester on an Agile team. Historically, the role of a Tester or QA has often been post-hoc, taking place after software has been created. Bob Martin, one of the original Agile manifesto signatories, observed that this was not optimal.
While, zero defects sounds very good to hear, is it really possible or is it an unachievable goal? Many organizations adopt a 'zero defects methodology'. Does it really mean anything?
A new form of an old question has been asked in the Behavior Driven Development community: is BDD merely Acceptance Test Driven Development done well? While the community calls out the differences, Dan North makes a request to avoid focusing on them, calling TDD "amazing".
Most of the discussion about cloud computing has focused on tools, providers, and security. While this focus is appropriate for an emerging technology, it becomes easier to recognize the value of cloud computing when you have actual application examples, or case studies. This month IBM announced two such applications: a development-and-test cloud, and an animation rendering cloud.
"Simplicity" is a core agile tenet, particularly when it comes to software design and testing. Since 2006, Naresh Jain has been running a worldwide conference, the Simple Design & Testing Conference, for practitioners to collectively push the boundaries on the topic. Naresh tells InfoQ what's going on behind this small, but well-known conference and why he is so passionate about the topic.
Automated tests that are brittle and expensive to maintain have led to companies abandoning test automation initiatives, according to Dale Emery. In a newly published paper, Dale shares some practical ways to avoid common problems with test automation. He starts with some typical automation code and evolves in ways that make it more robust, and less expensive to maintain.
James Bach and Elisabeth Hendrickson are two of the context driven testing community. James recently spoke at the STANZ conference and provided a guideline for approaching testing, and Elisabeth provides a heuristic checklist to help identify valuable testing activities.