Larissa Rocha

Larissa Rocha

Auto-generated profile, based on publicly available information

Larissa Rocha

UNEB / UEFS

Research Focus & Metrics

Academic Career Length

9Years (2018-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
8 September 2021 in Journal of Software Engineering Research and Development
Verified
Journal Article
Open access
PDF file
TVTássio Virgínio
Tássio Virgínio
LMLuana Martins
Luana Martins
RSRailana Santana
Railana Santana
ACAdriana Cruz
Adriana Cruz
LRLarissa Rocha
Larissa Rocha
IMIvan Machado
Ivan Machado
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
Verified
Journal Article
Open access
PDF file
NJNildo Silva Junior
Nildo Silva Junior
LMLuana Martins
Luana Martins
LRLarissa Rocha
Larissa Rocha
HCHeitor Costa
Heitor Costa
IMIvan Machado
Ivan Machado
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.

13 February 2021 in Journal of Software Engineering Research and Development
Verified
Journal Article
Open access
PDF file
LKLeila Karita
Leila Karita
BMBrunna Caroline Mourão
Brunna Caroline Mourão
LMLuana Almeida Martins
Luana Almeida Martins
LSLarissa Rocha Soares
Larissa Rocha Soares
IMIvan Machado
Ivan Machado
Sustainable computing is a rapidly growing research area spanning several areas of computer science. In the software engineering field, the topic has received increasing attention in recent years, with several studies addressing a range of concerns. However, few studies have demonstrated the awareness of software practitioners about the underlying concepts of sustainability in the software development practice. In this effect, this study aims to provide some evidence regarding the practitioners’ perception about the adoption of sustainability in software development, under four main perspectives: economic, social, environmental, and technical. In previous work, we carried out a preliminary survey study with twenty-five software engineers who work in a range of domains. The yielded results indicate an overall lack of knowledge about the topic, in particular, related to concepts about sustainable software. In this study, we extend the survey and reached a number of ninety-seven respondents. The novel results confirmed the evidence raised in the original survey that sustainability in the context of software is a new subject for software practitioners. However, professionals have shown interest in it. There is a general understanding that sustainability should be treated as a quality attribute. Among the observed perspectives, we generated an initial theory, which shows that software practitioners know the subject around ‘Green in Software’, even unconsciously. This study contributes to the green and sustainable software engineering field by bringing evidence on comprehending how the software industry understands the adoption of sustainability in the software development process.

25 September 2023
Verified
Conference Paper
Open access
Edna Dias CanedoEdna Dias Canedo
Edna Dias Canedo
LSLarissa Soares
Larissa Soares
GSGeovana Ramos Sousa Silva
Geovana Ramos Sousa Silva
VSVerônica Souza Dos Santos
Verônica Souza Dos Santos
FMFabiana Freitas Mendes
Fabiana Freitas Mendes
Context: It is known that men practitioners are predominant in software development teams over women. In recent years, researchers have investigated gender inequality from different perspectives, such as gender bias and suggestions to increase diversity in development teams. However, while most of the existing literature investigates the perception of women practitioners, the vast majority of the software development workforce – men – has received less attention. Goal: This work investigates men’s perceptions of gender inequality in software development teams and their experiences compared in software development to women. Method: Our study conducted a survey with 217 male practitioners, using a questionnaire consisting of 27 questions. The collected data was analyzed using a combination of quantitative and qualitative techniques, including graphical representations, percentages, and the grounded theory methodology. Results: Our findings reveal that most men do not perceive any sexist behavior among their team members and they are satisfied with the performance of their functions. In addition, their main suggestions to increase their participation in software development projects are offering training courses and improving the interaction among team members. Conclusions: The barriers and challenges that men practitioners face in software development teams are not the same as those faced by women. In addition, they consider that women do not work in software development due to a lack of affinity and knowledge about coding.

13 June 2022
Verified
Conference Paper
Closed access
PDF file
RSRailana Santana
Railana Santana
LMLuana Martins
Luana Martins
TVTássio Virgínio
Tássio Virgínio
LSLarissa Soares
Larissa Soares
HCHeitor Costa
Heitor Costa
IMIvan Machado
Ivan Machado
Test smells can reduce the developers' ability to interact with the test code. Refactoring test code offers a safe strategy to handle test smells. However, the manual refactoring activity is not a trivial process, and it is often tedious and error-prone. This study aims to evaluate RAIDE, a tool for automatic identification and refactoring of test smells. We present an empirical assessment of RAIDE, in which we analyzed its capability at refactoring Assertion Roulette and Duplicate Assert test smells and compared the results against both manual refactoring and a state-of-the-art approach. The results show that RAIDE provides a faster and more intuitive approach for handling test smells than using an automated tool for smells detection combined with manual refactoring.

30 September 2024
Verified
Conference Paper
Open access
PDF file
JOJhonatan Oliveira
Jhonatan Oliveira
LMLuigi Mateus
Luigi Mateus
TVTássio Virgínio
Tássio Virgínio
LRLarissa Rocha
Larissa Rocha
Test smells indicate potential issues or weaknesses within the test code, which can compromise its effectiveness and maintainability. They highlight areas where improvements can enhance the overall quality of the test suite or testing practices. For instance, an example of a test smell is the Anonymous Test, where the test’s name lacks descriptive information about its function or purpose. Addressing these test smells can result in more robust and maintainable test suites, thus improving the reliability of the testing process. Despite significant research on these issues, tools are scarce for automatically detecting them, particularly in certain programming languages such as JavaScript. In the current landscape, existing test smell detection tools for JavaScript lack intuitiveness and graphical interfaces, and require extensive configuration, which may lead to low adoption within the developer community. To address this gap, we propose SNUTS.js, a tool designed to streamline the detection of test smells in JavaScript. Designed as an API, SNUTS.js offers versatility, allowing integration with various tools and environments. This tool goes beyond existing solutions by identifying previously undetected test smells, including the Anonymous Test, Comments Only Test, Overcommented, General Fixture, Transcripting Test, and Sensitive Equality. We also introduce a new test smell termed Test Without Description, which denotes a test case lacking descriptive text. In a preliminary evaluation, we constructed a dataset of tests sourced from real-world projects on GitHub. Through manual analysis, we identified 285 instances of test smells. SNUTS.js demonstrated a detection accuracy of 100% for three specific types of test smells, Anonymous Test, Overcommented, and General Fixture, all tailored to the JavaScript environment. Link to the video: https://youtu.be/89z0jy4Nu0s