Complexity is a direct indicator of software quality and costs: if the complexity for any code is high, the quality of that code will be lower and it will cost more to manage it. Complexity measurements can be used to estimate development and test activities and to decide where refactoring is needed to improve quality and prevent problems.
Devices are becoming increasingly interconnected through the internet where they are communicating directly with each other. Testing such machine to machine (M2M) systems can be difficult due to their complexity and the usage of different platforms, as Peter Varhol explained in his talk about testing in the M2M world at the QA&Test 2014 conference.
By using Model Driven Development component tests could be skipped and integration and system testing went a lot smoother, said Bryan Bakker in the presentation Model Driven Development (MDD) and its impact on testing. Main results from the MDD approach are a reduction of the amount of testing and increased reliability of the code that was generated from a mathematical model.
Testability must be explicitly designed in the system said Peter Zimmerer from Siemens AG. Test architects should drive testability and collaborate with architects, designers and testers in using good design and engineering practices. At the QA&Test 2014 conference Peter gave a tutorial about design for testability for embedded software systems.
Last week VersionOne and CA Technologies announced that they have integrated their Project and Portfolio Management (PPM) and Agile Project Management (APM) products to provide an enterprise solution which the two organisations say gives users the ability to have a strategic view of a complete portfolio at the executive level no matter what methodology teams might use.
Testing embedded software and systems for the Internet of Things has to involve physical, sensory and emotional interactions says Gerie Owen, Business Solutions Analyst from Northeast Utilities. InfoQ interviewed Gerie Owen and Peter Varhol about how testing differs for the internet of things and embedded software and systems, and on dealing with expectations and experiences of people in testing.
The State of Testing 2013 report contains the results of a survey done by Joel Montvelisky from PractiTest together with Tea-Time with Testers. The survey, which has been filled in by people from testing and QA communities, provides insight in the adoption of test techniques and practices, test automation, and the challenges that testers are facing.
Testdroid's maker Bitbar has recently announced the integration of Testdroid mobile app testing products with Atlassian JIRA defect tracking system. InfoQ has interviewed Testdroid technical product manager Ville-Veikko Helppi to better understand how developers and organizations could benefit from it.
Satya Nadella, CEO at Microsoft Corporation, is preaching a more nimble approach of agile implementation to build software as part of the company’s transformation.
ISO/IEC/IEEE 29119 is a proposed standard for software testing that has generated a lot of reaction in the industry, much of it against the implementation of the new standard.
The 9th Annual State of Agile Survey is currently open for participants to share their adoption of Agile practices and processes for inclusion in the annual report.
One of the interesting features of the Task + async/await pattern is that you can easily decorate the results of any operation. Lucian Wischik of Microsoft shows how to take advantage of this in order to make your end-to-end testing more robust.
Cloud 9 has recently launched a new version of their online IDE. Usually, online developer tools are simpler than their native counterparts, some even refusing to call them IDEs. But Cloud 9 does not want to be just a rich editor, incorporating more and more features of a traditional integrated development environment.
Developing and delivering products which customers don’t want and for which there is no market can be costly. Agile can help you to efficiently develop products, but you need to know what to build. How can you find out which products your customers need?