Context. With the rapid development of mobile devices, mobile applications have occupied an increasingly large market. Software testing is an important factor in ensuring software quality [59]. In order to develop high-quality mobile applications, software companies are increasingly paying attention to mobile application testing. We found that there are relatively few studies on mobile application testing methods and tools in the real industry, and this direction of research has been very helpful for some software companies' mobile application testing, so we chose this direction for exploratory research. Objectives. The purpose of our research is to investigate the software company's field of mobile application testing. We mainly study the methods and tools of mobile application testing that are now popular in enterprises, the challenges faced by mobile application testing in software companies and how they solve challenges. Method. We used two methods to answer our research questions. We chose literature review and survey as research methods. The literature review method gives us an insight into the areas of expertise and mobile testing. Survey is used to answer our research questions. Our data collection method is the questionnaire survey method. When we completed the data collection, we performed statistics and analysis on the data and answered our research questions. Result. Through the literature review method, we summarize the methods and tools for mobile application testing in the literature. By sending 46 surveys to different software companies, we analyzed and analyzed the methods and tools for mobile application testing that are popular in the enterprise and the reasons for choosing these methods. We also listed the company's mobile application testing. Challenges and solutions encountered. Conclusions. We answered all the research questions. We analyzed the feedback from 46 questionnaires and got information about mobile application testing. We read a lot of literature and summarized the relevant conclusions in the literature. Our findings can help people in related fields, and we can provide them with 46 data and analysis results. We can also provide mobile application methods and tools that are popular among readers in the enterprise.

Context. With the rapid development of the software industry, innovative software products become the mainstream of the software market. Because software startups can use a few resources to quickly produce and publish innovative software products, more and more software startups are launched. Software testing is important to ensure the quality of product in software companies. Software testing is costly in software development, but if software testing is avoided, it could be costlier. Many different regular software companies spend up to 40-50% of development efforts on software testing [1] [2]. Compared with other regular software companies, time and money are finite and need to be allocated reasonably in software startups. Unreasonable allocation of time and money could lead to the failure of software startups. We don’t know how much software startups spend for testing, and few research studies have investigated the testing practices in software startups. Therefore, we decided to conduct an exploratory study to know about the testing practices in software startups. Objectives. The aim of the research is to investigate testing practices in software startups. In this study, we investigate software startups’ structure and how to manage their test team. The test processes and test techniques used in software startups have been researched. And the main testing challenges in software startups have been investigated as well. Methods. We mainly conducted a qualitative research for the study. We selected literature review and survey as the research method. The literature review method is used to get in-depth understanding of software testing practices in software companies. Survey is used to answer our research questions. We used interview as our data collection method. And in order to analyze data from interviews, we selected descriptive statistics method. Results. A total of 13 responses were obtained through interviews from 9 software startups. We got results from 9 investigated software startups to structure and manage their test teams. We analyzed the common steps of test processes and classified the techniques they used in the 9 software startups. At last, we analyzed and listed the main testing challenges that are occurred in the 9 software startups. Conclusions. The research objectives are fulfilled. The research questions have been answered. We got the conclusion based on 9 software startups. The 9 companies cannot represent all software startups, but we can know about test practices in software startups initially through the 13 interviews. We also found some differences about testing practice between 9 software startups and regular software companies. Our study is a primary research to explore testing practices in 9 software startups, we provided some data and analysis results of the 9 companies to the researchers who want to research some related area. In addition, our research could help someone who plans to set up a software company. They can use the data we collected to think about the testing practice in their own company. Then find out the best way to prevent and resolve the problem in testing.

Aspect-oriented programming is a relatively new programming paradigm and it builds on the basis of object oriented programming paradigm. It deals with those concerns that cross-cut the modularity of traditional programming mechanisms and it aims at reduction of code and to provide higher cohesion. As with any new technology aspect oriented programming provides some benefits and also there are some costs associated with it. In this thesis we have done a systematic review on aspect oriented software testing in the context of testing challenges. Detailed analysis have been made to show that how effective are the structural test techniques to handle these challenges. We have given the analysis of Aspect-oriented test techniques effectiveness, based on research literature. / Aspekt-orienterad programmering är ett relativt nytt programmering paradigm och det bygger på grundval av objektorienterad programmering paradigm. Det handlar om de farhågor som KORSSKUREN den modularitet av traditionell programmering mekanismer och det syftar till minskning av kod och för att ge högre sammanhållning. Som med all ny teknik aspekt-orienterad programmering ger vissa fördelar och det finns vissa kostnader associerade med den. I denna avhandling har vi gjort en systematisk översyn av aspekt orienterad mjukvara testning i samband med provning utmaningar. Detaljerad analys har gjorts för att visa att hur effektiva är de strukturella provmetoder för hantera dessa utmaningar. Vi har gett en analys av Aspect-oriented testa tekniker effektivitet, baserade på forskningslitteratur. / FOLKPARKSVAGEN 18 Room 03 Ronneby 37240 Sweden Mobile Number Kashif 073-9124604, Amar 073-6574048

Currently, information technology is influencing every walks of life. Our livesincreasingly depend on the software and its functionality. Therefore, thedevelopment of high-quality software products is indispensable. Also, inrecent years, there has been an increasing interest in the demand for high-qualitysoftware products. The delivery of high-quality software products and services isnot possible at no cost. Furthermore, software systems have become complex andchallenging to develop, test, and maintain because of scalability. Therefore, withincreasing complexity in large scale software development, testing has been acrucial issue affecting the quality of software products. In this paper, large-scalesoftware testing challenges concerning quality and their respective mitigations arereviewed using a systematic literature review, and interviews. Existing literatureregarding large-scale software development deals with issues such as requirementand security challenges, so research regarding large-scale software testing and itsmitigations is not dealt with profoundly.In this study, a total of 2710 articles were collected from 1995-2020; 1137(42%)IEEE, 733(27%) Scopus, and 840(31%) Web of Science. Sixty-four relevant articleswere selected using a systematic literature review. Also, to include missed butrelevant articles, snowballing techniques were applied, and 32 additional articleswere included. A total of 81 challenges of large-scale software testing wereidentified from 96 total articles out of which 32(40%) performance, 10(12 %)security, 10(12%) maintainability, 7(9 %) reliability, 6(8%) compatibility, 10(12%)general, 3(4%) functional suitability, 2(2%) usability, and 1(1%) portability weretesting challenges were identified. The author identified more challenges mainlyabout performance, security, reliability, maintainability, and compatibility qualityattributes but few challenges about functional suitability, portability, and usability.The result of the study can be used as a guideline in large-scale software testingprojects to pinpoint potential challenges and act accordingly.

Submitted by Alison Vanceto (alison-vanceto@hotmail.com) on 2017-05-09T12:58:24Z No. of bitstreams: 1 DissBRS.pdf: 3255630 bytes, checksum: e4d94f1ee923813cfd91e76e992dbfa8 (MD5) / Approved for entry into archive by Ronildo Prado (ronisp@ufscar.br) on 2017-06-01T18:49:57Z (GMT) No. of bitstreams: 1 DissBRS.pdf: 3255630 bytes, checksum: e4d94f1ee923813cfd91e76e992dbfa8 (MD5) / Approved for entry into archive by Ronildo Prado (ronisp@ufscar.br) on 2017-06-01T18:50:12Z (GMT) No. of bitstreams: 1 DissBRS.pdf: 3255630 bytes, checksum: e4d94f1ee923813cfd91e76e992dbfa8 (MD5) / Made available in DSpace on 2017-06-01T19:49:40Z (GMT). No. of bitstreams: 1 DissBRS.pdf: 3255630 bytes, checksum: e4d94f1ee923813cfd91e76e992dbfa8 (MD5) Previous issue date: 2016-06-30 / Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq) / Fundação de Amparo à Pesquisa do Estado de São Paulo (FAPESP) / Context: Traditional testing approaches, considering the context of Adaptive Systems (ASs), have been evaluated incipiently and superficially with respect to their effectiveness in identifying faults. It is very clear the challenge of guaranteeing the correctness of ASs, due to the adaptive properties of these systems. Thus, the following question raises: how to characterise adequately and broadly the difficulties for testing ASs? There is not an approach that is driven by challenges found in the literature. Goals: In this work, we analysed and characterised the challenges faced by the testing activity when applied to ASSs. By characterising the challenges, we investigated testing strategies based on them. Methodology: In order to achieve the goals, we performed the following steps: (i) characterising the state-of-art of testing of ASs, using a Systematic Literature Review (SLR); (ii) investigating the challenges in source codes of real ASs that are available online in source code repositories; (iii) defining the testing strategy named T, based on the characterised challenges; (iv) defining the testing strategy T* based on the challenges and comprised by three testing approaches; (v) evaluating the effectiveness of the strategies T and T*; and (vi) investigating the challenges along the application of T and T*. Results: the main results were: (i) a characterisation of fine-grained and coarse-grained challenges for testing ASs; and (ii) two testing strategies based on such challenges. We evaluated the strategies by running an exploratory study which encompassed one AS and both testing strategies. Conclusion: The characterisation of challenges supported the definition and execution of the testing strategies. These strategies were able to reduce the impact of the challenges and to identify faults in the AS. / Contexto: Abordagens de teste tradicionais sao ainda incipientes e superficialmente avaliadas quanto a sua efetividade em revelar defeitos em Sistemas Adaptativos (SAs). E nítido o desafio de garantir a corretude de SAs levando-se em consideração as características de adaptacao desses sistemas, culminando na seguinte pergunta: como caracterizar adequadamente, de forma abrangente, as dificuldades para se testar SAs? Na literatura nao foi encontrada qualquer estrategia de teste que seja guiada por desafios de teste caracterizados. Objetivos: Neste trabalho buscou-se compreender e caracterizar os desafios impostos a atividade de teste de SAs. Uma vez caracterizados, os desafios, propos-se investigar estrategias de teste baseadas nestes desafios. Metodologia: Para atingir o objetivo seguiram-se as etapas: (i) caracterizacao do estado da arte por meio de uma Revisao Sistematica (RS); (ii) investigacao da existencia de desafios de teste em SAs presentes em repositórios de código-fonte; (iii) definho de uma estrategia de teste, denominada T, com base nos desafios caracterizados da RS; (iv) definicao de uma estrategia de teste combinada, denominada T*, composta por três abordagens de teste; (v) avaliaçao da efetividade das estrategias T e T*; e, por fim, (vi) investigacao da presença dos desafios nos SAs analisados, por meio das estrategias T e T*. Resultados: Os principais resultados foram: (i) uma caraterizacao de desafios para o teste de SAs; e (ii) e uma definicao de estrategias de teste baseadas nos desafios caracterizados. A avaliacao foi realizada com a aplicacao de um estudo exploratório, utilizando um SA, de uma estrategia de teste somente baseada em desafios (T) e de uma estrategia de teste baseada em desafios combinada com outras abordagens (T*), a fim de comparar os resultados de ambas as estrategias. Conclusão: A caracterizacao dos desafios auxiliou na definicao e execucao de estrategias de teste, as quais mitigaram os desafios presentes nos SAs e puderam identificar defeitos.