Considerations for Regression Testing Process in Agile Development Environments

Testing is central piece in agile development methodology, that fast is taking roots and at the same time it is becoming challenging, in particular due to short time periods between incremental updates of the software, as such the time for overall testing including regression testing is becoming limited. In regression testing, the changed code as well as certain portion of existing code that is impacted is to be retested. Intuitively, it seems that the best option is to automate the regression testing. However, precisely due to time constraints the automation approach is proving to be challenging for regression testing in agile development environments. As the time to create and update these automation scripts will become limiting factor in case of overnight/weekly releases. Regression testing in agile development environments should be using some prioritization of tests for next cycle to enable timely regression testing. We can use the information of future release plans, defined by the specifications for each release, and prioritize the test cases as we write them. As there can be information available for future release cycles (as there are releases in planned for short intervals) we can have some methods of using this information and make the process of regression testing process in future more effective and efficient. In this paper, we present a technique of using future builds (new enhancements, features, or fixes) to select test cases on a class of software which is used for interconnecting diverse systems in near real time fashion. The results are encouraging and the technique can be used to guide regression testing process in agile development environment.

Download Full-text

Using a Low Code Development Environment to Teach the Agile Methodology

Lecture Notes in Business Information Processing - Agile Processes in Software Engineering and Extreme Programming ◽

10.1007/978-3-030-78098-2_12 ◽

2021 ◽

pp. 191-199

Author(s):

Mary Lebens ◽

Roger Finnegan

Keyword(s):

Higher Education ◽

Digital Transformation ◽

Comfort Level ◽

Agile Development ◽

Development Environment ◽

Business World ◽

Development Platform ◽

Agile Methodology ◽

Development Methodology ◽

Code Development

AbstractThe Agile development methodology is soaring in popularity in the business world. Companies are turning to Agile to develop products quickly and to achieve digital transformation of their organization. Because of this push, companies need employees who understand Agile. Therefore, higher education is obligated to provide an understanding of Agile to students as they enter the workplace. Providing Agile experience to students who are new to programming is difficult because they are so worried about the coding aspects of the assignment, they cannot take time to think about the methodology they are using. The coding crowds out the time needed to get an understanding of how Agile actually works. One remedy for this is to use a low or no-code development platform. With this type of platform students spend less time learning to create apps, freeing them to experience the rituals and roles of Agile. This study examines using the Agile methodology along with the Microsoft Power Apps platform to provide an Agile experience to students. Two course sections were surveyed to learn if students perceived that they acquired a better understanding of Agile and to learn their perceptions of a no-code platform experience. The students completed surveys to ascertain their comfort with the Agile methodology and whether the no-code environment increased their comfort level. The results showed students perceived the no-code platform increased their comfort with using the Agile methodology. The implication is that no-code platforms can be used broadly to help students to gain experience with Agile.

Download Full-text

Biochemical and Histopathological Evaluation of the Radioprotective Effects of Melatonin Against Gamma Ray-Induced Skin Damage

Current Radiopharmaceuticals ◽

10.2174/1874471012666181120163250 ◽

2019 ◽

Vol 12 (1) ◽

pp. 72-81 ◽

Cited By ~ 11

Author(s):

Dheyauldeen Shabeeb ◽

Masoud Najafi ◽

Ahmed Eleojo Musa ◽

Mansoor Keshavarz ◽

Alireza Shirazi ◽

...

Keyword(s):

Gamma Ray ◽

Histopathological Examination ◽

Radical Scavenging ◽

Limiting Factor ◽

Skin Damage ◽

Exposed Skin ◽

Male Wistar Rats ◽

Time Periods ◽

Skin Damages ◽

The Right

Background:Radiotherapy is one of the treatment methods for cancers using ionizing radiations. About 70% of cancer patients undergo radiotherapy. Radiation effect on the skin is one of the main complications of radiotherapy and dose limiting factor. To ameliorate this complication, we used melatonin as a radioprotective agent due to its antioxidant and anti-inflammatory effects, free radical scavenging, improving overall survival after irradiation as well as minimizing the degree of DNA damage and frequency of chromosomal abrasions.Methods:Sixty male Wistar rats were randomly assigned to 4 groups: control (C), melatonin (M), radiation (R) and melatonin + radiation (MR). A single dose of 30 Gy gamma radiation was exposed to the right hind legs of the rats while 40 mg/ml of melatonin was administered 30 minutes before irradiation and 2 mg/ml once daily in the afternoon for one month till the date of rat’s sacrifice. Five rats from each group were sacrificed 4, 12 and 20 weeks after irradiation. Afterwards, their exposed skin tissues were examined histologically and biochemically.Results:In biochemical analysis, we found that malondialdehyde (MDA) levels significantly increased in R group and decreased significantly in M and MR groups after 4, 12, and 20 weeks, whereas catalase (CAT) and superoxide dismutase (SOD) activities decreased in the R group and increased in M and MR groups during the same time periods compared with the C group (p<0.05). Histopathological examination found there were statistically significant differences between R group compared with the C and M groups for the three different time periods (p<0.005, p<0.004 and p<0.004) respectively, while R group differed significantly with MR group (p<0.013). No significant differences were observed between C and M compared with MR group (p>0.05) at 4 and 20 weeks except for inflammation and hair follicle atrophy, while there were significant effects at 12 weeks (p<0.05).Conclusion:Melatonin can be successfully used for the prevention and treatment of radiation-induced skin injury. We recommend the use of melatonin in optimal and safe doses. These doses should be administered over a long period of time for effective radioprotection and amelioration of skin damages as well as improving the therapeutic ratio of radiotherapy.

Download Full-text

Identifying Effective Test Cases through K-Means Clustering for Enhancing Regression Testing

2013 12th International Conference on Machine Learning and Applications ◽

10.1109/icmla.2013.109 ◽

2013 ◽

Cited By ~ 14

Author(s):

Yulei Pang ◽

Xiaozhen Xue ◽

Akbar Siami Namin

Keyword(s):

Regression Testing ◽

Test Cases

Download Full-text

Data Collection for Investigating Speech Variability in A Specific Speaker Over Long and Short Time Periods

2005 International Conference on Natural Language Processing and Knowledge Engineering ◽

10.1109/nlpke.2005.1598725 ◽

2006 ◽

Author(s):

S. Tsuge ◽

M. Shishibori ◽

Fuji Ren ◽

K. Kita ◽

S. Kuroiwa

Keyword(s):

Data Collection ◽

Speech Variability ◽

Time Periods ◽

Short Time

Download Full-text

Regression Testing-Based Requirement Prioritization of Mobile Applications

International Journal of Systems and Service-Oriented Engineering ◽

10.4018/jssoe.2012100102 ◽

2012 ◽

Vol 3 (4) ◽

pp. 20-39 ◽

Cited By ~ 1

Author(s):

Varun Gupta ◽

D. S. Chauhan ◽

Kamlesh Dutta

Keyword(s):

Mobile Applications ◽

Development Process ◽

Regression Testing ◽

Test Cases ◽

Application Development ◽

High Quality ◽

Ripple Effects ◽

Software Application ◽

Mobile Software ◽

Requirement Prioritization

Mobile software application development process must be matured enough to handle the challenges (especially market related) associated with the development of high quality mobile software development. Ever increasing number of both mobile users and mobile applications had presented software engineers with the challenge of satisfying billions of users with high quality software applications to be delivered within deadline and budgets. Always there had been a lot of pressure to develop complex software categorized by thousands of requirements, under resource constrained environment. Requirement prioritization is one of the activities undertaken by software engineer to deliver partial software product to its customers such that most important requirements are implemented in the earliest releases. During next releases some changed and pending requirements are implemented, an activity that generates ripple effects. Such ripple effects need to be tested by executing modified source code against test cases of previous releases (regression testing). Regression testing is a very effortful activity that requires a software tester to select test cases that have high fault detection capability, execute the modified code against selected test cases and performing debugging. This regression testing activity can be lowered to the maximum extend by considering dependencies between requirements during the time of requirement prioritization. Thus requirement prioritization will be carried out not only against aspects like cost, time, risks, business values etc but against dependencies also. The aim is to implement almost all dependent highest priority requirements in current release so that implementation of new requirements is unlikely to have ripple effects. Changes in requirements might not be related to variable usage and definition and might not involve a change in functionality. In such cases there is no need to select already executed test cases of previous versions. Module dependencies can lead to test case selections of previous versions if changes of requirement lead to ripple effects. This paper aims to implement highest priority requirements such that regression testing is performed to minimum thereby improving development process of mobile applications. The proposed technique had been successfully evaluated on Android based notification software application that meets the specification of Aakash tablets.

Download Full-text

Agile Software Development Process Applied to the Serious Games Development for Children from 7 to 10 Years Old

International Journal of Information Technologies and Systems Approach ◽

10.4018/ijitsa.2015070105 ◽

2015 ◽

Vol 8 (2) ◽

pp. 64-79 ◽

Cited By ~ 4

Author(s):

Sandra P. Cano ◽

Carina S. González ◽

César A. Collazos ◽

Jaime Muñoz Arteaga ◽

Sergio Zapata

Keyword(s):

Serious Games ◽

User Profile ◽

Extreme Programming ◽

Agile Development ◽

User Centered Design ◽

Medium Development ◽

Development Methodology ◽

Agile Software ◽

The City

The development of video games is a complex, multidisciplinary process, which involves different areas as well as a greater number of roles than for traditional software. Serious games face process constraints that concern a number of interactive, educational and psychological factors designed to lead to the fulfillment of educational objectives within a specific context. Based on a case study in the city Cali, Colombia, an iterative and incremental process is proposed, focusing on small and medium development for educational serious games and basing itself on two lines of research: agile development methodology and user-centered design (UCD) for children from 7 to 10 years. The agile methodology eXtreme Programming (XP) offers a useful option for the development of serious games as it establishes a continuous communication with all project stakeholders - including the end user - throughout the project, while UCD allows the user profile to be known and identified so that the game will meet the needs and match the capabilities, expectations and motivations of the child.

Download Full-text

Using Fuzzy Logic in Test Case Prioritization for Regression Testing Programs with Assertions

The Scientific World JOURNAL ◽

10.1155/2014/316014 ◽

2014 ◽

Vol 2014 ◽

pp. 1-9 ◽

Cited By ~ 7

Author(s):

Ali M. Alakeel

Keyword(s):

Fuzzy Logic ◽

Regression Testing ◽

Test Case ◽

Test Cases ◽

Test Case Prioritization ◽

Software Developers ◽

Novel Approach ◽

History Of ◽

Supporting Tool

Program assertions have been recognized as a supporting tool during software development, testing, and maintenance. Therefore, software developers place assertions within their code in positions that are considered to be error prone or that have the potential to lead to a software crash or failure. Similar to any other software, programs with assertions must be maintained. Depending on the type of modification applied to the modified program, assertions also might have to undergo some modifications. New assertions may also be introduced in the new version of the program, while some assertions can be kept the same. This paper presents a novel approach for test case prioritization during regression testing of programs that have assertions using fuzzy logic. The main objective of this approach is to prioritize the test cases according to their estimated potential in violating a given program assertion. To develop the proposed approach, we utilize fuzzy logic techniques to estimate the effectiveness of a given test case in violating an assertion based on the history of the test cases in previous testing operations. We have conducted a case study in which the proposed approach is applied to various programs, and the results are promising compared to untreated and randomly ordered test cases.

Download Full-text

An efficient effort and cost estimation framework for Scrum Based Projects

International Journal of Engineering & Technology ◽

10.14419/ijet.v7i4.12.20992 ◽

2018 ◽

Vol 7 (4.12) ◽

pp. 52

Author(s):

Mohit Arora ◽

Dr. Sahil Verma ◽

Dr. Kavita

Keyword(s):

Cost Estimation ◽

Process Models ◽

Agile Development ◽

Software Systems ◽

Effort Estimation ◽

Related Factors ◽

Inappropriate Use ◽

Business Units ◽

Development Methodology ◽

Soft Computing Techniques

Software Process Models from its inception instill standardization and creates a generic culture of developing software for various IT industries. A great paradigm shift has been observed in terms of embracing Agile Development methodology as a viable development methodology in cross key business units. There is a buffet of agile methodologies comes under the umbrella of ASD, out of which Scrum got the highest popularity and acceptability index. Agile based software development is the need of immediate environment. There is an increasing demand for significant changes to software systems to meet ever-changing user requirements and specifications. As Agile is volatile, so effort estimation is challenging and still striving for perfection to decide size, effort, cost, duration and schedule of projects with minimum error. This cause sensitizes potential researchers all across the globe to start working on addressing the issue of inaccurate predication of efforts. The gap between estimated and actual effort is because of limited or no inclusion of various estimation factors like people and project related factors, inappropriate use of size metric and cost drivers, ignorance of testing effort, team member’s inability to understand user story size and complexity etc. This paper attempts to bridge the gap of estimated and actual effort by the use of soft computing techniques thus taking the research to advance frontier area in terms of estimation.

Download Full-text