There is a lot more to software development than simply writing code. Quality and error-free function play the main roles and a range of test procedures ensure that the developed software truly satisfies the requirements. While manual test procedures require a lot of the company's resources and take up a lot of time because of their sequential nature, the latest tools and approaches are now providing ever better support for the automated testing of software.
In the past, testing often just concentrated on whether software ran without any errors (code coverage, e.g., with NCover, dotCover; code analysis, e.g., with ReSharper, NArrange; module tests, e.g., with JUnit/NUnit). In the meanwhile, however, more attention is being paid to the correlation of the results achieved with the requirements set, whereby the use of suitable test management software is becoming ever more important. The idea is to detect deviations early and correct them in order to keep the project on track. Continuous integration, e.g., using a Hudson server or Microsoft Team Foundation Server (TFS), automatically validates all changes to the source code "overnight" to inform the project manager quickly and comprehensively.
In other words, the earlier the tests are performed in the software development life cycle (SDLC), the sooner it is possible to deliver error-free software which complies with the requirements. With our approach of test automation during the development stage we can make error-free software available more quickly than ever before. We are happy to assist and support our customers with their test automation – both using the conventional V/W model procedure and in agile environments (Scrum).
infoteam employs a wide range of tools and processes to ensure the high quality of the software to be developed. We develop in accordance with the ideas and specifications of clean code development on the one hand and work in compliance with standards (IEEE 730, 828, 829, 830, 1012, 1016, 1058) in accordance with the specifications of different standard committees on the other.
Coordinated tools are used in the individual phases of the test process each time:
Depending on the development phase of the software project and the type of test, it is necessary to ensure almost seamless integration of the tools in the existing development environment. In addition, different approaches such as the use of mock-ups or click demos allow earlier inclusion of the testers – from departments other than IT too – and as such allow early exchange.
Although test automation means increased efforts at the beginning of the project, the investment pays for itself after just two or three iterations.
We happily support our customers in the creation of the test concept and the test specification as well as setting up the correct test environment. The following test methods are possible: SiL (software-in-the-loop test), HiL (hardware-in-the-loop test), risk-based testing, FMEA (Failure Mode and Effects Analysis), FMECA (Failure Mode and Effects and Criticality Analysis), model-based testing (MBT), functional tests, user story tests, unit tests, component tests, smoke tests, usability tests, acceptance tests, performance tests, stability testing, scalability testing.
We are also happy to assist as your competent partner for the evaluation and documentation of test results and the further development and maintenance of the test environment.
All our developers are qualified ISTQB © Certified Testers and boast many years of experience on different projects in a wide range of sectors.