Archive
Blog - posts for April 2019
Apr 24 2019
Cyrille Artho, KTH Associate Professor
Mutation testing can serve as indicators on test quality and relevance
How do you see mutation testing tools being adopted in business projects, as an effective method with significant benefits on distributed software updates?
I think mutation testing has its uses in specialized settings, where the software is small (or well-modularized). However, many companies struggle with the fact that they can't keep up with testing, so we also see the opposite (test selection), where tests are not analyzed as much in depth, but instead, the goal is to be as light-weight as possible. From this point of view, mutation techniques should in general also be efficient and light-weight.
Apr 17 2019
STAMP talks at Devoxx Paris
STAMP is presented at Devoxx Paris, through two conferences.
Date: 17-19 April 2019
Place: Paris
Click below for more Devoxx Paris information, video, presentation and photos.
Apr 12 2019
Mutation Testing Workshop at Ericsson HQ in Stockholm
Date: Friday 12 April, 2019
Place: Ericsson Offices, building 18, Torshamngatan 23 Kista Stockholm
Room: LM Junior Conference room
Hours: 09:00AM - 04:00PM
Speaker: Oscar Luis Vera Pérez (Inria Rennes)
Apr 11 2019
Test Automation Research for Industry Workshop in Stockholm
TESTOMAT, STAMP, XIVT & Software Center are organising in Stockholm a one-day workshop with leading researchers in test automation. They're sharing their work to help businesses reach the next level of test automation. This unique event consists of presentations as well as showcasing tools with topics covering latest research in test automation.
It is an opportunity for industry representatives and experts to collaborate with researchers and to discuss how the latest test automation research can transform the current costlier and less effective way of testing.
Apr 09 2019
Plenary meeting in Stockholm, April 9-10
Meeting Place: KTH central campus
map
Lindstedtsvägen 5
Room:D31
More about the plenary meeting (login required): Stockholm Plenary meeting on private wiki
Apr 04 2019
Lars Thomas Boye, Tellu IoT Senior Software Developer
Test amplification has a great potential to cover multiple contexts and configurations
How would you present STAMP?
For me, STAMP is about helping organizations who develop software to test that software, thereby increasing software quality. It uses amplification to address the need to do more testing while also reducing the effort needed to increase test coverage and quality. For a company selling software, or services based on software developed in-house, software quality is vital, and testing is the way to insure quality.
Apr 02 2019
Search-Based Test Case Implantation for Testing Untested Configurations
Publication: Information and Software Technology
Authors: Dipesh Pradhan, Shuai Wang, Tao Yue, Shaukat Ali, Marius Liaaen
URL: https://www.sciencedirect.com/science/article/pii/S0950584919300540?dgcid=rss_sd_all
Title: Search-Based Test Case Implantation for Testing Untested Configurations
Context
Modern large-scale software systems are highly configurable, and thus require a large number of test cases to be implemented and revised for testing a variety of system configurations. This makes testing highly configurable systems very expensive and time-consuming.
Objective
Driven by our industrial collaboration with a video conferencing company, we aim to automatically analyze and implant existing test cases (i.e., an original test suite) to test the untested configurations.
Method
We propose a search-based test case implantation approach (named as SBI) consisting of two key components:
1) Test case analyzer that statically analyzes each test case in the original test suite to obtain the progr am dependence graph for test case statements and
2) Test case implanter that uses multi-objective search to select suitable test cases for implantation using three operators, i.e., selection, crossover, and mutation (at the test suite level) and implants the selected test cases using a mutation operator at the test case level including three operations (i.e., addition, modification, and deletion).
Results
We empirically evaluated SBI with an industrial case study and an open source case study by comparing the implanted test suites produced by three variants of SBI with the original test suite using evaluation metrics such as statement coverage (SC), branch coverage (BC), and mutation score (MS). Results show that for both the case studies, the test suites implanted by the three variants of SBI performed significantly better than the original test suites. The best variant of SBI achieved on average 19.3% higher coverage of configuration variable values for both the case studies. Moreover, for the open source case study, the best variant of SBI managed to improve SC, BC, and MS with 5.0%, 7.9%, and 3.2%, respectively.
Conclusion
SBI can be applied to automatically implant a test suite with the aim of testing untested configurations and thus achieving higher configuration coverage.