Improving Traceability Recovery Between Bug Reports and Manual Test Cases

Software testing is a process where you have the stated requirements, pre-requisite software that is to be installed and the configuration of the machine that need to be done as per the test data for the test case and for a specific platform which when verified works perfectly. This paper describes about Manual test case process overview in the testing life cycle for a large software development project and how you track the effort for the same. A Tester need to know about the fundamentals of testing concepts. Documentation of the testing concepts and the process overview of the testing life cycle for a software product need to be done initially so that a new tester when recruited can understand the basic flow as to how it is carried out in real time in an organization practically. Initially a tester need to execute the manual test case for few platforms and some tougher manual test cases need to be learnt from the tester who is having some experience. The tougher manual test cases need to be identified initially from the experienced tester who will be giving a session for the execution of such test cases. So when the foundation for a new tester is powerful the plan assigned for the execution of test cases is met. The effort tracking for the testing can be captured for a tester and should be matched with planned effort for the execution of test cases. Measurement of the testing effort plays a very important role as to how comfortable a new tester is and further root cause analysis is done if required when the new tester does not meet the planned effort.

Download Full-text

A TOOL FOR OPTIMAL MANUAL TEST CASES SELECTION

Proceedings of 10th CONTECSI International Conference on Information Systems and Technology Management ◽

10.5748/9788599693094-10contecsi/ps-154 ◽

2013 ◽

Author(s):

Lorena do Carmo Caldas ◽

Antônio M. da S. Pitangueira

Keyword(s):

Test Cases ◽

Manual Test

Download Full-text

Method for Automatically Generating Test Cases for Web Services

Xibei Gongye Daxue Xuebao/Journal of Northwestern Polytechnical University ◽

10.1051/jnwpu/20183610149 ◽

2018 ◽

Vol 36 (1) ◽

pp. 149-155

Author(s):

Jun Hou ◽

Hong Zhou ◽

Chunyan Ma ◽

Jiangbin Zheng

Keyword(s):

Web Service ◽

Formal Model ◽

Automatic Generation ◽

Theoretical Research ◽

Test Case ◽

Test Cases ◽

Complex Data ◽

Data Types ◽

Operation Test ◽

Manual Test

Because manual test case design is time-consuming and laborious and has certain blindness and inclination, Web service testing is based on WSDL document and formal model tree automatic generation. The theoretical research and Web service single operation test case generation method. Web service operation test case method, and to build test tools. The application results show that this method can greatly save the time of manually analyzing the complex data types in WSDL files and the time of generating the test cases according to the test cases of built-in data types. It simplifies the generation of test cases, and prepares test cases.

Download Full-text

ESPRET: A tool for execution time estimation of manual test cases

Journal of Systems and Software ◽

10.1016/j.jss.2018.09.003 ◽

2018 ◽

Vol 146 ◽

pp. 26-41 ◽

Cited By ~ 1

Author(s):

Sahar Tahvili ◽

Wasif Afzal ◽

Mehrdad Saadatmand ◽

Markus Bohlin ◽

Sharvathul Hasan Ameerjan

Keyword(s):

Execution Time ◽

Time Estimation ◽

Test Cases ◽

Manual Test

Download Full-text

Automated Event-Triggered GUI Testing and Bug Reproduction for Non-Android Applications

International Journal of Innovation in Enterprise System ◽

10.25124/ijies.v5i02.99 ◽

2021 ◽

Vol 5 (02) ◽

pp. 172-181

Author(s):

Anit Thomas M ◽

Chinchu Krishna S

Keyword(s):

Use Cases ◽

Test Cases ◽

Natural Languages ◽

Bug Reports ◽

Novel Approach ◽

German Regions ◽

Android Applications ◽

Manual Testing ◽

Almost All ◽

Test Result

Today’s mobile gadgets are seamlessly incorporating innovative features demanded by the users. Most often, the applications contain bugs or functionality issues reported by the customers. The developers are responsible for reproducing such reported bugs, which are written in natural languages. Reproducing bugs from bug reports make the bug resolution inefficient. Nowadays, various methods are adopted to reproduce crash reports for android applications. But bug reproduction for non-android applications is still a challenging task. This paper proposes a novel approach that is capable of doing bug reproduction from bug reports to help the developers to solve the functionality issues of non-android applications in an automated manner. This approach uses a UI tester called the GUI engine, which is an excel sheet. The use cases which are to be tested can be filled in the GUI engine. All the use cases are to be filled based on a particular syntax. For that purpose, the developer can make use of a set of yaml files containing all the GUI information for all the screens of the application under test. The use cases are executed in the GUI engine and conclusions are made based on the test result. The GUI engine displays two colors green and red showing the working and failing of GUI components of the application under test. So that the developer can easily identify the failing components and take actions accordingly. The test has been done with more than 1000 test cases for one region and the result shows that almost all GUI components work for this method except for animation. It has tested for software developed for US, Europe, and German regions. Also, the proposed method is found to be much faster and efficient than the existing as well as manual testing methods.

Download Full-text

The significance of bug report elements

Empirical Software Engineering ◽

10.1007/s10664-020-09882-z ◽

2020 ◽

Vol 25 (6) ◽

pp. 5255-5294

Author(s):

Mozhan Soltani ◽

Felienne Hermans ◽

Thomas Bäck

Keyword(s):

Statistical Analysis ◽

Open Source ◽

Open Source Software ◽

Test Cases ◽

Software Projects ◽

Software Debugging ◽

Bug Reports ◽

Bug Report

Abstract Open source software projects often use issue repositories, where project contributors submit bug reports. Using these repositories, more bugs in software projects may be identified and fixed. However, the content and therefore quality of bug reports vary. In this study, we aim to understand the significance of different elements in bug reports. We interviewed 35 developers to gain insights into their perceptions on the importance of various contents in bug reports. To assess our findings, we surveyed 305 developers. The results show developers find it highly important that bug reports include crash description, reproducing steps or test cases, and stack traces. Software version, fix suggestions, code snippets, and attached contents have lower importance for software debugging. Furthermore, to evaluate the quality of currently available bug reports, we mined issue repositories of 250 most popular projects on Github. Statistical analysis on the mined issues shows that crash reproducing steps, stack traces, fix suggestions, and user contents, have statistically significant impact on bug resolution times, for ∼70%, ∼76%, ∼55%, and ∼33% of the projects. However, on avarage, over 70% of bug reports lack these elements.

Download Full-text