The use of websites and mobile applications has become essential for numerous daily activities. However, not everyone can have full access to such services and content due to many websites and applications being inaccessible to people with disabilities, such as people with vision impairments. In this context, even though developers may demonstrate an effort to create more accessible content, there is limited information about the characteristics of different accessibility assessment methods applied to websites and mobile applications. Thus, the present study aimed to perform a meta-analysis of 38 types of accessibility problems on websites and mobile applications extracted from 38 studies in the literature from an initial search of 304 articles. Studies carried out automated assessments using tools, expert-based inspections and user testing involving disabled people. The results confirm other considerations made in the literature, showing that automated evaluation methods have significant limitations on an adequate coverage of accessibility problems, covering less than 40% of the types of problems found on websites and less than 20% on mobile apps. A significant percentage of problems both on mobile and web platforms were only encountered by studies involving users. Expert inspection showed a higher coverage of problems encountered by users, both on mobile apps and on websites, despite not covering all of them. Thus, the article concludes by showing a consolidation of literature data to reinforce that effective accessibility evaluations of web and mobile applications should count in expert-based inspections and user tests involving people with disabilities.
8 September 2021 in Journal of Software Engineering Research and Development
Several strategies have supported test quality measurement and analysis. For example, code coverage, a widely used one, enables verification of the test case to cover as many source code branches as possible. Another set of affordable strategies to evaluate the test code quality exists, such as test smells analysis. Test smells are poor design choices in test code implementation, and their occurrence might reduce the test suite quality. A practical and largescale test smells identification depends on automated tool support. Otherwise, test smells analysis could become a cost-ineffective strategy. In an earlier study, we proposed the JNose Test, automated tool support to detect test smells and analyze test suite quality from the test smells perspective. This study extends the previous one in two directions: i) we implemented the JNose-Core, an API encompassing the test smells detection rules. Through an extensible architecture, the tool is now capable of accomodating new detection rules or programming languages; and ii) we performed an empirical study to evaluate the JNose Test effectiveness and compare it against the state-of-the-art tool, the tsDetect. Results showed that the JNose-Core precision score ranges from 91% to 100%, and the recall score from 89% to 100%. It also presented a slight improvement in the test smells detection rules compared to the tsDetect for the test smells detection at the class level.
8 September 2021 in Journal of Software Engineering Research and Development
Developing test code may be a time-consuming process that requires much effort and cost, especially when done manually. In addition, during this process, developers and testers are likely to adopt bad design choices, which may lead to introducing the so-called test smells in the test code. As the test code with test smells size increases, these tests might become more complex, and as a consequence, much more challenging to understand and evolve them correctly. Therefore, test smells may harm the test code quality and maintenance and break the whole software testing activities. In this context, this study aims to understand whether software testing practitioners unintentionally insert test smells when they implement test code. We first carried out an expert survey to analyze the usage frequency of a set of test smells and then interviews to reach a deeper understanding of how practitioners deal with test smells. Sixty professionals participated in the survey, and fifty professionals participated in the interviews. The yielded results indicate that experienced professionals introduce test smells during their daily programming tasks, even when using their companies’ standardized practices. Additionally, tools support test development and quality improvement, but most interviewees are not aware of test smells’ concepts.
18 January 2023 in Journal of Software: Evolution and Process