Software Testing: Achievements, Challenges, Dreams

This article reviews the achievements, challenges, and dreams in the field of software testing. It discusses the intention and content of the article, research methods used, findings, problems highlighted, and the relevance of the conclusion to software testing.

Software Testing
Research:
Achievements,
Challenges, Dreams
ARTICLE REVIEW

Introduction
 Software Engineering is a sector of computer that deals with the
physical systems of software systems and its development,
deployment, management and testing with the application of
theoretical principles.
 The article would focus on the following aspects of the article:
 Intention and Content of the Article
 Research Method described in the Article
 Findings of the Article
 Problems or Issues Highlighted
 Conclusion of the Article and its relevance to software testing

Discussion
 Intention and Content of the Article
 The author mostly focuses on the subject of software testing in this
particular paper as well as the ways by which industry has a widespread
validation approach towards this particular subject. The author identifies
how even after the identification of the validation approach of software
testing in the industry, the process of Software Testing is still extremely
relevant and expensive for the purpose.

 Research Method described in the Article
 The research method that has been approached in this particular article to
identify the approaches of the software testing methodologies and the ways
by which it has been executed towards the findings of the article with the
help of this article is conducted through qualitative secondary research
method.
 The author also identifies that the organizations in the previous times have
only used software testing technologies as a quality assurance mechanism
that would help in maintaining the quality of the developed software to find
its feasibility according to the requirement of the clients as well as the
organizational standards.
Discussion

 Findings of the Article
 The article points have gone through several researches regarding the
software testing methodologies and the ways by which the organizations
have been using it as a quality assurance technology.
 The author highlights its findings by various samples of specific aspects
through the sample observations. The various observations are
characterized through the questions like Why, How, How Much, What, Where
and When.
Discussion

 Problems or Issues Highlighted
 The highlighted problems or issues that the author have identified in this
particular article can be listed as below:
 The article highlights all the process related issues that are aligned to the
technical aspects of the software testing methodologies used.
 The main issue that has been found about the processes in the software testing
method is the lack of conciseness for making the procedure as abstract as
possible. The lack in understanding of the conciseness leads to several problems
in implementing the appropriate software testing methodology.
Discussion

 Conclusion of the Article
 The conclusion of the article enunciates the phase where the researcher has
pointed out that there creeps up the challenges in software testing
methodologies. The author points out how model based derivations of the
test cases can be conciliated so that it can be appropriate for the
dynamically evolving systems.
Discussion

 Relevance of the conclusion to software testing
 The destination of this article has been categorised into four goals, which
are addressed by the author as ‘dreams’. Thus the author had defined how
the differences between the approaches and the dreams would be solved
with the appropriate methodologies adopted.
Discussion

Conclusion
 In conclusion it can be said that the article that has been reviewed in
this regard for testing the software has categorically focused on all the
aspects of software testing and this has been elaborated through the
findings of the author.

Conclusion
 They are mostly focused on finding the relevant differences that the
software possesses at a particular stage that is different than the
requirement of the user or a client. In addition to that, this technique
clarifies how the software is different to or closer to the standardized
software specifications, or by what degree is the software able to
determine the robustness or stressful load conditions.

References
Bertolino, A., 2007, May. Software testing research: Achievements, challenges,
dreams. In 2007 Future of Software Engineering (pp. 85-103). IEEE Computer
Society.
Briand, L., Nejati, S., Sabetzadeh, M. and Bianculli, D., 2016, May. Testing the
untestable: model testing of complex software-intensive systems. In Proceedings
of the 38th international conference on software engineering companion(pp. 789-
792). ACM.
Garousi, V. and Mäntylä, M.V., 2016. A systematic literature review of literature
reviews in software testing. Information and Software Technology, 80, pp.195-216.
Takanen, A., Demott, J.D., Miller, C. and Kettunen, A., 2018. Fuzzing for software
security testing and quality assurance. Artech House.