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.

Submitted by Luciana Ferreira (lucgeral@gmail.com) on 2014-08-01T14:00:30Z No. of bitstreams: 2 license_rdf: 23148 bytes, checksum: 9da0b6dfac957114c6a7714714b86306 (MD5) DissertacaoFinalGilmarCC.pdf: 1781002 bytes, checksum: 864dc93f98977e9c6364e12bcc473c58 (MD5) / Made available in DSpace on 2014-08-01T14:00:30Z (GMT). No. of bitstreams: 2 license_rdf: 23148 bytes, checksum: 9da0b6dfac957114c6a7714714b86306 (MD5) DissertacaoFinalGilmarCC.pdf: 1781002 bytes, checksum: 864dc93f98977e9c6364e12bcc473c58 (MD5) Previous issue date: 2012 / Fundação de Amparo à Pesquisa do Estado de Goiás - FAPEG / Software Testing is part of software quality assurance activities. It aims to uncover the presence of defects, that can be inserted in various stages of software develop- ment. Several techniques are used in the testing activity, highlighting the functional ones, which derive test requirements from the software specification. The research faces the problem of how to evolve the functional testing strategies with low costs, relative to the amount of test cases needed, without compromising the number of uncovered defects. A systematic review was planned and executed, based on formu- lated questions so as to answer the research problem. Such review supported the definition of a new criterion for functional testing, the Systematic Functional Test with Decision Table Application (TFS-DT), which is an extension of Systematic Software Testing (TFS) and provides joint application of criteria: Partitioning Equi- valence Classes, Boundary Value Analysis and Decision Table. The TFS-DT defines a strategy based on a set of requirements and has a process in order to apply the strategy in a systematic manner. Three empirical studies were applied with promi- sing results compared to TFS: all of them reduces at least half the adequated set without impact on the number of uncovered defects. / Teste de Software faz parte das atividades de garantia da qualidade do software. Destina-se a revelar a presen ̧ca de defeitos, que podem ser inseridos em v ́arios est ́agios do desenvolvimento do software. V ́arias t ́ecnicas s ̃ao usadas na atividade de teste, com destaque para as funcionais, que derivam requisitos de teste a partir da especifica ̧c ̃ao do software. A pesquisa enfrenta o problema de como evoluir as estrat ́egias de testes funcionais reduzindo o custo, em rela ̧c ̃ao `a quantidade de casos de teste necess ́arios, sem comprometer o n ́umero de defeitos revelados. Uma revis ̃ao sistem ́atica foi planejada e executada, com base em quest ̃oes formuladas de modo a responder ao problema da pesquisa. Esta revis ̃ao apoiou a defini ̧c ̃ao de um novo crit ́erio de teste funcional, o Teste Funcional Sistem ́atico com Aplica ̧c ̃ao da Tabela de Decis ̃ao (TFS-TD), que ́e uma extens ̃ao do Teste Funcional Sistem ́atico (TFS) e que prevˆe a aplica ̧c ̃ao conjunta dos crit ́erios: Particionamento em Classes de Equivalˆencia, An ́alise do Valor Limite e Tabela decis ̃ao. O TFS-TD define uma estrat ́egia baseada em um conjunto de diretrizes e possui um processo para aplicar esta estrat ́egia de forma sistem ́atica. Trˆes estudos emp ́ıricos foram aplicados com resultados promissores em rela ̧c ̃ao ao TFS: todos eles reduzem, pelo menos, pela metade o conjunto adequado, sem impacto na quantidade de defeitos revelados.