No abstract

A flaky test is a test which could fail or pass for the same version of a certain software code. In continuous software development environments, flaky tests represent a problem. It is difficult to get an effective and reliable testing pipeline with a set of flaky tests. Also, according to many practitioners, despite the persistence of flaky tests in software development, they have not drawn much attention from the research community. In this paper, we describe how a company faced this issue, and implemented solutions to solve flaky tests for REST web services. The paper concludes proposing a set of key success factors for stopping flaky tests in this type of testing.

Abstract. Currently and in recent years several international initiatives specifically oriented to put together small and medium enterprises, processes and agile methods have been identified. Likewise, different studies have identified the mapping between agile methodologies and software development process models like CMMI-DEV and ISO/IEC 12207, but the studies related to ISO/IEC 12207 are based on the 1995 version. Therefore this work focuses on the relationship between agile practices, especially SCRUM, and a process subset from the 2008 version of the ISO/IEC 12207 standard. SCRUM is one of the most popular agile methods and is an incremental iterative process. These two characteristics mean dividing the project into phases or iterations and incremental delivery of the project. The relationships indicated in the work are obtained from the analysis of previous works and consulting experience at 25 enterprises that comply with the standard outcomes implementing agile methodologies. The main purpose of the study is to know the extent to which agile practices help in the implementation of practices indicated in this process model.

Many users access web pages from different browsers looking for the same user experience in all of them. However, there are several causes that produce compatibility issues. Those defects affect functionalities and user interface components. In this paper we present a systematic literature review which aims to find and summarize existing techniques, tools and challenges related to cross-browser testing. According to the results, the most used technique is the visual analysis. However, there are still challenges to face. The most important challenge is the identification of dynamic components in the user interface. Cross-browser compatibility topics are getting importance according to an increment in published articles. Nevertheless, there are techniques that are not completely developed yet and do not fully support test automation practices.

Data-driven storytelling helps to communicate facts, easing comprehension and decision making, particularly in crisis settings such as the current COVID-19 pandemic. Several studies have reported on general practices and guidelines to follow in order to create effective narrative visualizations. However, research regarding the benefits of implementing those practices and guidelines in software development is limited. In this article, we present a case study that explores the benefits of including data visualization best practices in the development of a software system for the current health crisis. We performed a quantitative and qualitative analysis of sixteen graphs required by the system to monitor patients' isolation and circulation permits in quarantine due to the COVID-19 pandemic. The results showed that the use of storytelling techniques in data visualization contributed to an improved decision-making process in terms of increasing information comprehension and memorability by the system stakeholders.