Search

Agile methods adopted in the software industries have given a new edge as well as scope to software outcomes. To determine anomalies that has been triggered by analytic hierarchical process (AHP) o...

Software testing is a continuous process during the software development stages to ensure quality software products. Researchers, experts and software engineers keep going on studying new techniques, methods and approaches of testing to accommodate changes in software development because of the flexible requirement along with the changing of technology. So, developers and testers need to have effective methods, tools and approaches to create a high-quality product at an efficient cost. This paper provides an effective approach for context-driven testing (CDT) in an agile software development process. CDT is a testing approach that supports the tester to choose their testing techniques and test objectives based on specific contexts. The aim of this paper is to propose an effective approach for implementing the CDT in practice, called CDTiP. Through an analysis of two case studies using an agile development process with different contexts, we validate the effectiveness of the approach in terms of test coverage, detect errors, test effort. The empirical results show that CDTiP is suitable for the agile development process that can help the tester to detect defects faster at minimum cost. The results of this method have been applied at Enclave, an ODC Software Engineering company, on real projects.

Software systems become increasingly complex and testing is a vital component of the development process. Teaching software testing concepts are now more than ever acknowledged as essential. The aim of this paper is to report on our software testing teaching approach, using game-based activities to engage students and facilitate learning, making them aware of their actions and related testing concepts. Agile testing and Session-Based Test Management are learned through lego-based context, exploratory testing is learned through a dice-based game, and various testing concepts are learned during the laboratory using storification. We report on the results of activities with students, extracting valuable lessons for reproducing this approach in teaching software testing: game-based learning motivated students to participate in the activities, reflection on their actions allowed them to self-discover the testing concepts encapsulated into the game. In addition, we adapt and analyse an industry-like environment that serves as experience for their future careers.

Context. Software testing effort estimation is one of the important problems in software development and software testing life cycle. The object of the study is the process of estimating the agile testing efforts for small Web projects. The subject of the study is the multiple regression models for estimating the agile testing efforts for small Web projects. Objective. The goal of the work is the creation of the multiple non-linear regression model for estimating the agile testing efforts for small Web projects on the basis of the Johnson multivariate normalizing transformation. Method. The model, confidence and prediction intervals of multiple non-linear regression for estimating the agile testing efforts for small Web projects are constructed on the basis of the Johnson multivariate normalizing transformation for non-Gaussian data with the help of appropriate techniques. The techniques based on the multiple non-linear regression analysis using the multivariate normalizing transformations to build the models, equations, confidence and prediction intervals of multiple non-linear regressions are used. The techniques allow to take into account the correlation between random variables in the case of normalization of multivariate non-Gaussian data. In general, this leads to a reduction of the mean magnitude of relative error, the widths of the confidence and prediction intervals in comparison with the linear models and nonlinear models constructed using univariate normalizing transformations. Results. Comparison of the constructed model with the linear model and non-linear regression models based on the decimal logarithm and the Johnson univariate transformation has been performed. Conclusions. The multiple non-linear regression model to estimate the agile testing efforts for small Web projects is firstly constructed on the basis of the Johnson multivariate transformation for SB family. This model, in comparison with other regression models (both linear and non-linear), has a smaller value of the mean magnitude of relative error, smaller widths of the confidence and prediction intervals. The prospects for further research may include the application of other multivariate normalizing transformations and data sets to construct the multiple non-linear regression model for estimating the agile testing efforts for small Web projects.

Agile testing approaches test-driven development (TDD), behavior-driven development (BDD); have gained popularity since the introduction of agile practices. The concept of using these approaches in software projects is to help projects succeed. The effect of TDD and BDD on Project success factors namely, cost, time, and customer satisfaction/external quality, remains an area of investigation. Therefore, this study investigates the results of previously published articles on the effect of TDD and BDD on project success factors. A systematic literature review has been conducted considering articles published between 1999 up to 2020. Thirty-one studies were selected and analyzed. 74.1% of studies are experiments, 25.8% are case studies. 67.7% of these studies were performed in an industrial setting, 29.0% were performed in an academic setting and only one study with 3.22% was mixed academic and industrial settings. The result shows that the TDD and the BDD consume more time and cost compared to traditional testing (TLD). Moreover, the TDD as TLD may not necessarily satisfy the customer unlike the BDD appears that achieve customer satisfaction. Although, when TDD compared to BDD, TDD consumed more time and lower customer acceptance than the BDD.

Management includes the tasks planning, organization, management, and control of an activity. A project manager is someone who plans, organizes, monitors, and controls a project. To be able to do this, they need knowledge, experience, information, and competence. To understand the management of agile testing, we first have to take a careful look at how agile projects work: In most agile process models such as Scrum, Kanban, Extreme Programming and Lean Management, testing is not is explicitly addressed as we know it from traditional models—it is implicitly assumed that this is of course covered by the agile teams. The test is therefore inextricably linked to the development. There may be testers, i.e., specialists with a focus on quality assurance and acceptance testing, but a separate test track does not appear in most process models. Team members with a test focus thus cover several roles: on the one hand that of the tester, on the other hand that of the test manager and finally that of the quality manager.

The consistent use of test automation is the only chance to ensure the quality of each potentially deliverable product at the end of each sprint. However, many aspects must be clarified and defined for maintainable and efficient test automation. These include the organizational and technical integration into DevOps environments and processes, the selection of suitable automation tools, the design of an automation framework, and the organization and planning of automation activities and automated test executions within or synchronized with the development sprints. If required, test automation know-how also needs to be established within the team. This is a challenge to most teams, but this investment needs to be considered as there is no successful agile testing without test automation.

It is known that quantitative measures for the reliability of software systems can be derived from software reliability models. And, as such, support the product development process. Over the past four decades, research activities in this area have been performed. As a result, many software reliability models have been proposed. It was shown that, once these models reach a certain level of convergence, it can enable the developer to release the software. And stop software testing accordingly. Criteria to determine the optimal testing time include the number of remaining errors, failure rate, reliability requirements, or total system cost. In this paper we will present our results in predicting the reliability of software for agile testing environments. We seek to model this way of working by extending the Jelinski-Moranda model to a ‘stack’ of feature-specific models, assuming that the bugs are labelled with the feature they belong to. In order to demonstrate the extended model, several prediction results of actual cases will be presented. The questions to be answered in these cases are: how many software bugs remain in the software and should one decide to stop testing the software?

Agile testing is not a single phase testing, commonly it is performed till the end of software development life cycle. An agile testing team is responsible for the error free quality product. So the testers in agile team should be dynamic in nature to adopt the abrupt changes in system; today’s testing industry is striving for rapid software delivery with keeping in view the changing customer requirements. Agile testing approach has evolved to address the necessities of dynamic environment in which traditional approaches were failing to cope with. It has the cutting edge like fast release and minimum documentation which results in maximizing speed and profit. However, the most difficult task is to make the decision such that the agile testing method should be chosen according to the given requirements of a particular project. In the absence of empirical work, an approach is proposed using the world widely accepted methods as Analytic Hierarchy Process (AHP). The calculated results from multi criteria decision making and the final result is evaluated using the rank aggregation methods. This work would prove to be a pivotal point in the field of agile testing as it includes these empirical methods which provide the much awaited authenticity and reliability, which sometimes is questioned in case of testing approach.

Documentation has always been a controversial theme in software development. Even the Agile Manifesto positions itself on this topic with the statement “Working software over comprehensive documentation”, which many saw as a license to completely get rid of the often tiresome topic of documentation. This also strikes a chord with those who believe that the only valid documentation for a software application is the program code itself, and in order to describe everything a program does, the additional documentation would have to be as comprehensive as the program itself, i.e. including all conditions and branches and loops. Accordingly, the documentation would be the same as the program code, only in a different language. Contrary to these polarizing views, this chapter takes a more differentiated look at various types of documentation, their different creators, users and their purposes. These aspects and the need to maintain documentation should be considered in advance and in the spirit of Lean Management, a Lean Documentation approach should be defined for each individual project.

This chapter examines multiple approaches, all of which have proven to be useful models in the respective project environment. Thus, the applicability of the traditional test process according to ISTQB in the agile context is considered and the Four Test Quadrants in Agile Testing are discussed. Another important topic for agile companies is scaling - therefore the approaches LeSS and SAFe are briefly presented. Additionally, case studies are outlined to illustrate what an agile test organization can look like.

In order to better understand the cultural change towards agile software development and to understand “Agile Testing” not only as a buzzword, it is important to take a look into the past. Much of what we perceive today as common knowledge has its justification in the methodical and technical progress of software technology in the last 30 years. Experience is an essential element for innovation and improvement. For example, the average age of the signatories of the Agile Manifesto in 2001 was about 47 years and back then, it wasn’t just about doing everything differently, it was about doing it better. This is often overlooked when “agile” is used to simply get rid of unpleasant things or to hide one’s own weaknesses. The approach to develop software in a cooperative, benefit-oriented, and efficient way, is the core of the agile idea.

The advances in Machine Learning (ML) require software organizations to evolve their development processes in order to improve the quality of ML systems. Within the software development process, the testing stage of an ML system is more critical, considering that it is necessary to add data validation, trained model quality evaluation, and model validation to traditional unit, integration tests and system tests. In this paper, we focus on reporting the lessons learned of using model testing and exploratory testing within the context of the agile development process of an ML system that predicts lawsuits proneness in energy supply companies. Through the development of the project, the SCRUM agile methodology was applied and activities related to the development of the ML model and the development of the end-user application were defined. After the testing process of the ML model, we managed to achieve 93.89 accuracy; 95.58 specificity; 88.84 sensitivity; and 87.09 precision. Furthermore, we focused on the quality of use of the application embedding the ML model, by carrying out exploratory testing. As a result, through several iterations, different types of defects were identified and corrected. Our lessons learned support software engineers willing to develop ML systems that consider both the ML model and the end-user application.

Mestrado em Gestão de Sistemas de Informação As metodologias ágeis são cada vez mais utilizadas na indústria de desenvolvimento de software, especialmente pela sua facilidade na incorporação de alterações a requisitos de cliente ao longo de um projeto. Este tema surge associado ao mestrado em gestão de sistemas de informação, enquadrando-se o projeto desenvolvido como uma aplicação prática de conceitos estudados. Adicionalmente, fase de testes de sistema e de integração foi que mais experienciei durante os projetos de desenvolvimento de software. Assim, o objetivo deste projeto passou por evidenciar os testes efetuados ao software, ao passo que é utilizada a metodologia ágil SCRUM em todo o ciclo de vida do projeto empresarial. Ao longo do trabalho apresentado, são abordadas as técnicas no que concerne ao teste de uma aplicação de tickets de aprovisionamento de rede. Os testes são uma parte importante do projeto, uma vez que têm um grande impacto na qualidade do software entregue ao cliente. Consequentemente, é exposto como se desenlaça esta fase do projeto. O ponto chave de aprendizagem foi a comunicação ser um ponto fulcral, quer entre o cliente e a equipa, quer entre os membros da equipa para o projeto ser concluído com sucesso. O feedback do cliente no momento dos testes é de extrema relevância. Além disso, o facto de fazer os testes de sistema ao longo do projeto, em vez de apenas quando os desenvolvimentos estão terminados para todos os requisitos, permitiu que os tempos de entrega fossem mais curtos. Agile methodologies are more commonly used on software development, especially for its easiness on incorporating changes requirements during a project. The agile methodologies subject is part of the master?s degree in management of information systems program, framing the project developed as a practical application of studied concepts. In addition, software development projects have an associated life cycle, and the system and integration testing phases were what I experienced most during the projects I developed at the business level. Thus, the objective of this project was to highlight the tests carried out on the software, while the SCRUM agile methodology is used throughout the life cycle of the project. Throughout the work presented as practical, its techniques are addressed about testing an application of network provisioning tickets. Tests are an important part of the project, as they have a major impact on the quality of the software delivered to the customer. Consequently, it is exposed how the test phase goes. The test cases presented were developed and executed according to the processes presented and following the assumptions of the agile SCRUM methodology. The key learning point was communication being a focal point, either between the client and the team, or between team members for the project to be successfully completed. Customer feedback at the time of testing is extremely important. In addition, the fact that system tests are carried out throughout the project, instead of only when developments are complete for all requirements, allowed delivery times to be shorter. info:eu-repo/semantics/publishedVersion

Background: The artifacts used in Agile software testing and the reasons why these artifacts are used are fairly well-understood. However, empirical research on how Agile test artifacts are eventually designed in practice and which quality factors make them useful for software testing remains sparse. Aims: Our objective is two-fold. First, we identify current challenges in using test artifacts to understand why certain quality factors are considered good or bad. Second, we build an Activity-Based Artifact Quality Model that describes what Agile test artifacts should look like. Method: We conduct an industrial survey with 18 practitioners from 12 companies operating in seven different domains. Results: Our analysis reveals nine challenges and 16 factors describing the quality of six test artifacts from the perspective of Agile testers. Interestingly, we observed mostly challenges regarding language and traceability, which are well-known to occur in non-Agile projects. Conclusions: Although Agile software testing is becoming the norm, we still have little confidence about general do's and don'ts going beyond conventional wisdom. This study is the first to distill a list of quality factors deemed important to what can be considered as useful test artifacts. © 2020 IEEE Computer Society. All rights reserved. open access

The software engineering industry has witnessed an increasing number of innovative methods and practices in the last decade at different levels, ranging from development processes to software projects and from testing to verification software products. Extensive studies have been conducted empirically to investigate and discuss the impact of using agile principles in the testing process on distributed teams across geographical boundaries. This empirical study has a similar focus, using a real case study in a distributed domain and applying agile testing to a selected team, compares their outcome with another three teams to determine the impact of involving a client in a testing process to overcome distributed development challenges. The findings indicate a highly positive impact on team productivity when using agile tests as compared with other groups using central distributed team testing. All teams met a 90% testing requirement. However, the group applying agile testing verified more than 99% of all requests entered into the testing process, a notable difference supporting the productivity of any development project.

The goal of any business is to satisfy the needs of its target customers, and IT industry is not an exception from that rule. Thus, the upgraded version of the V-model testing is supposed to deal with the weaknesses of the original version in question by combining it with the method known as agile testing. At the beginning of the report, hypothesis such as the strengths and weaknesses of the existing V-model testing via literature review and interviews with respective specialists in the sphere were analysed. Successively, the possible advantages of agile method of testing were then considered. Moreover, the report comes up with the ways in which the two models could be naturally combined to produce a much more effective one. Once the new model was presented, its strengths and weaknesses were assessed by the means of a case study analysis using metric and a data analysis through a survey were conducted to evaluate the credibility of the futurist model. Promptly, the research found that the suggested testing model provides better results than the common version of V-model testing. Firstly, a real case scenarios under metric evaluation of the models have indicated that the proposed model is better than the V-model, since it can handle the following aspects; reduced testing time, debugging, prioritization of requirements, easy mapping of roles and improved visibility of project resources. Secondly, a survey data analysis highlighted various advantages of the future model. The top priorities of the new model from the respondent’s perception were; the new model manages rapidly changing priorities, it accelerates time to market, it increases productivity and it improves quality.

The research is based on the characteristics of instructional software of evaluation and exercise, taking a small examination system for driving license as an example, this study is devoted to exploring a feasible test method for instructional software of evaluation and exercise based on mobile platform. The test method consists of four testing phases of unit and integration testing, functionality testing, comprehensive testing and teaching evaluation which existed research of functionality testing for modern Android mobile Apps is fully used for reference. Furthermore, further work is put forward. Firstly, a special defect management database for bug definition and analysis needs to be established. Secondly, major test points in comprehensive testing phase should be converted to user stories in modern agile testing environment for software exploratory test methods positively.