Search

Android set-top boxes, often known as STBs, have emerged as a popular option for streaming and viewing digital content. Testing Android STBs, however, can be extremely difficult due to the complicated hardware and software configurations they require. In addition to being time-consuming and error-prone, manual testing can be exceedingly costly. Because of this, automation testing has emerged as a possible solution to the problems that have been identified. This article presents an overview of the current state of the art in automation testing for Android STBs from a technical perspective. This article highlights the difficulties typically connected with testing Android STBs, the advantages of automation testing, and the various tools and methods utilised for automation testing. Integrating AI and machine learning approaches are explored to demonstrate the potential for increasing efficiency and adaptability in Android STB automation testing. The findings contribute to the evolution of testing techniques for Android STBs by providing insights into tool selection, performance optimisation, and future approaches for intelligent automation. In addition, the article provides an overview of recent research conducted in this area and an analysis of the current and future directions that automation testing for Android STBs will take. [ABSTRACT FROM AUTHOR]

Anchor bolts are often used for fixing information boards, supports, and soundproof walls in various facilities. Corrosion of anchor bolts and fatigue cracks occur frequently due to the various external environments, and visual inspection and hammering inspection are mainly used. In visual inspection, it is difficult to confirm corrosion or fatigue cracks of anchor bolts in the area where foundations, nuts, and base plates are installed. Additionally, the hammering inspection is easily affected by the surrounding environment and the subjective reaction of the tester. Therefore, it is necessary to develop a method that can easily and accurately detect defects such as cracks and corrosion occurring in anchor bolts installed in road facilities using non-destructive testing techniques. In this paper, the possibility and reliability of anchor bolt defects such as corrosion and cracks were experimentally verified by applying ultrasonic inspection among non-destructive inspection techniques for anchor bolt maintenance. [ABSTRACT FROM AUTHOR]

Purpose: The purpose of this paper is to explore the condition of managing manual software testers. Design/methodology/approach: The analysis is based on a survey targeting three groups (managers, testers, development team members) that will touch on areas consistent with the management functions. Findings: The condition of testers’ management can be described as good, but there is a probability of improvement for the areas that have been studied. Research limitations/implications: It’s worth carrying out similar research on larger samples to make sure about the obtained averages values and statistical differences between them. It’s also worth proposing methods to improve the possible problematic areas that have been found in this research paper. Practical implications: This paper may draw the attention of managers whose subordinates are software testers that there are areas where they can improve their management. Originality/value This research shows how testers’ management is perceived by managers, how it is perceived by testers and how it is perceived by other members of development teams. [ABSTRACT FROM AUTHOR]

Software Testing is the series of actions to seeking the error defects in the software. It mean, probe carry with comprehensive information of the quality of software underneath the test. Software Testing tools allow the developer and tester to proceed the work in a way of effortlessly which gives the path as computerize practice of difficult in the software progress, Generally, testing arise as manual or automated where the comparison is passes between the expected results with the actual result, In these days, Automated Software testing is high ranking for software projects so as to naturally validate and verify numerous process of the project. The goal of this scrutiny is ti assess and reconcile the automated software testing tools such as QTP, Selenium and Load Runner to dig out their usability, performance, legibility. This study helps the developer and tester to select the apt tool depends on their needed. [ABSTRACT FROM AUTHOR]

Test case prioritization is an important testing activity, in practice, specially for large scale systems. The goal is to rank the existing test cases in a way that they detect faults as soon as possible, so that any partial execution of the test suite detects the maximum number of defects for the given budget. Test prioritization becomes even more important when the test execution is time consuming, for example, manual system tests versus automated unit tests. Most existing test case prioritization techniques are based on code coverage, which requires access to source code. However, manual testing is mainly performed in a black-box manner (manual testers do not have access to the source code). Therefore, in this paper, the existing test case prioritization techniques (e.g. diversity-based and history-based techniques) are examined and modified to be applicable on manual black-box system testing. An empirical study on four older releases of desktop Firefox showed that none of the techniques were strongly dominating the others in all releases. However, when nine more recent releases of desktop Firefox, where the development has been moved from a traditional to a more agile and rapid release environment, were studied, a very significant difference between the history-based approach and its alternatives was observed. The higher effectiveness of the history-based approach compared with alternatives also held on 28 additional rapid releases of other Firefox projects - mobile Firefox and tablet Firefox. The conclusion of the paper is that test cases in rapid release environments can be very effectively prioritized for execution, based on their historical failure knowledge. In particular, it is the recency of historical knowledge that explains its effectiveness in rapid release environments rather than other changes in the process. Copyright © 2016 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

Copyright of Revista Antioqueña de las Ciencias Computacionales is the property of Instituto Antioqueno de Investigacion and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Software test processes are complex and costly. To reduce testing effort without compromising effectiveness and product quality, automation of test activities has been adopted as a popular approach in software industry. However, because test automation usually requires substantial upfront investments, automation is not always more cost-effective than manual testing. To support decision-makers in finding the optimal degree of test automation in a given project, we recently proposed a process simulation model using the System Dynamics modeling technique and used the simulation model in the context of a case study with a software company in Calgary, Canada. With the help of the simulation model, we were able to evaluate the performance of test processes with varying degrees of automation of test activities and help testers choose the most optimal cases. The goal of the earlier study was to investigate how the simulation model can help decision-makers decide whether and to what degree the company should automate their test processes. In this article, we present further details of the System Dynamics model, its usage scenarios and examples of simulation experiments independent from a specific company context. Copyright © 2015 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]

Manual software testing is a widely practiced verification and validation method that is unlikely to fade away despite the advances in test automation. In the domain of manual testing, many practitioners advocate exploratory testing (ET), i.e., creative, experience-based testing without predesigned test cases, and they claim that it is more efficient than testing with detailed test cases. This paper reports a replicated experiment comparing effectiveness, efficiency, and perceived differences between ET and test-case-based testing (TCT) using 51 students as subjects, who performed manual functional testing on the jEdit text editor. Our results confirm the findings of the original study: 1) there is no difference in the defect detection effectiveness between ET and TCT, 2) ET is more efficient by requiring less design effort, and 3) TCT produces more false-positive defect reports than ET. Based on the small differences in the experimental design, we also put forward a hypothesis that the effectiveness of the TCT approach would suffer more than ET from time pressure. We also found that both approaches had distinctive issues: in TCT, the problems were related to correct abstraction levels of test cases, and the problems in ET were related to test design and logging of the test execution and results. Finally, we recognize that TCT has other benefits over ET in managing and controlling testing in large organizations. [ABSTRACT FROM AUTHOR]

Copyright of Revista Antioqueña de las Ciencias Computacionales is the property of Instituto Antioqueno de Investigacion and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)