International Telemetering Conference Proceedings / November 04-07, 1991 / Riviera Hotel and Convention Center, Las Vegas, Nevada / The Telemetry Test Station has been developed at the Digital Systems Division, ISRO Satellite Centre, to test House Keeping Telemetry Packages which will be flown onboard satellites. The main feature of the Test Staion is its configurability, since it is intended to be used with different types of (low bit rate) telemetry packages. Other features include automation of test procedure, and reduction in testing time/increase in repeatability due to minimisation of manual interaction. Since the test station comprises GPIB controlled equipment, hardware and software, thf configurability should be built in at all levels and stages, from design to implementation. Thus since the specification is subject to change, the configuration for structure of the system is traosferred from the designer to the user. This results in a large part of the system being devoted to user interface design, since the computer which is an integral part of the setup must be ‘invisible’ to the user. Due to specialised requirements the user and the system are treated at peer level i.e, at any time during the entire test session, the user can override system process and verify/correct it and equally, the system must also verify/correct user input especially with regard to critical test procedures. The test tession itself (after configuration) is divided into three equally important sections: preprocessing, test and analysis. All the data required during the test run should be made ready before the actual test. Since it has been found by experience that this is not always convenient, the preprocessing software is integrated in to the test session so that the user can perform this at any time. Similarly, the results of the test can also be analysed immediately or even during the test to improve subsequent procedures. This paper describes the prototype telemetry test station which has been built and tested over the past two years. This performance has been satisfactory. The system integration features and design problems and solution are high lighted.

With the development of Advanced Driving Assistance Systems (ADAS) vehicles have undergone better experience in field of safety, better driving and enhanced vehicle systems. Today these systems are one of the fastest growing in automotive domain. Physical parameters like map data, vehicle position and speed are crucial for the advancement of functionalities implemented for ADAS. All the navigation map databases are stored in proprietary format. So for the ADAS application to access this data an appropriate interface has to be defined. This is the main aim of Advance Driver Assistant Systems Interface Specifications (ADASIS) consortium. This new specification allows a coordinated effort of more than one industry to improve comfort and fuel efficiency. My research during the entire duration of my master thesis mainly focuses on two stages namely XML Comparator and CAN stream generation stages from ADASIS Test Environment that was developed in our company. In this test environment ADASIS Reconstructor of our company is tested against the parameters of Reference Reconstructor provided by ADASIS consortium. The main aim of this environment is to develop a Reconstructor which will adhere to all the specifications given in ADASIS Reconstructor. My implementation in this master thesis focuses on two stages of test environment setup which are XML Comparison and CAN Stream Generation Tool respectively. Prior to my working, these stages lacked in-depth research and usability features for further working.

International Telemetering Conference Proceedings / November 04-07, 1991 / Riviera Hotel and Convention Center, Las Vegas, Nevada / Early in the 1980s White Sands Missile Range (WSMR) began studying the problem of updating the Telemetry Tracking Systems (TTS) used to support test range missions. The information and equipment available at that time indicated that very little technology advancement had occurred in the area of TTS. Because the TTS usually have a long service life, it was imperative that the new or updated systems be as good as the state-of-the-art in todays technology could produce. Because of the lack of technology advancements, it was evident that drastic measures would be required to achieve the objectives of the update effort. These findings resulted in a program called the Advanced Telemetry Tracking System Integration and Development (ATTSID). Its objective was to determine if it was possible to apply advanced computer technology to the solution of servosystem problems characteristic in most TTS. This paper and three related papers, The Advanced Telemetry Tracking Servosystem; An Automated Testing System for a Telemetry Tracking System; and The Microcomputer-based Digital Controller for the Advanced Telemetry Tracking System; document the objectives, design considerations, fabrication and evaluation of a prototype TTS. It utilizes a dedicated computer system to control, compensate the servo position loop, and provide automated testing of the servo and RF receiving systems. This computer system was installed and evaluated in one of the WSMR Transportable Telemetry Acquisition Systems (TTAS) for evaluation and refinement of the system. The results of this program will determine the evolution of TTS and extend the use of computer technology to providing more reliable and accurate telemetry tracking support of test range operations.

International Telemetering Conference Proceedings / October 25-28, 1999 / Riviera Hotel and Convention Center, Las Vegas, Nevada / Emerging technologies in the field of "Test & Measurement" have recently enabled the development of the Rapidly Adaptable Instrumentation Tester (RAIT). Based on software developed with LabVIEW®, the RAIT design enables quick reconfiguration to test and calibrate a wide variety of telemetry systems. The consequences of inadequate testing could be devastating if a telemetry system were to fail during an expensive flight mission. Supporting both open-bench testing as well as automated test sequences, the RAIT has significantly lowered total time required to test and calibrate a system. This has resulted in an overall lower per unit testing cost than has been achievable in the past.

Software testing is the process of executing a program with the intention of finding errors in the code. It is the process of exercising or evaluating a system or system component by manual automatic means to verify that it satisfies specified requirements or to identify differences between expected and actual results [4]. Software Testing should not be a distinct phase in System development but should be applicable throughout the design development and maintenance phases. ‘Software Testing is often used in association with terms verification & validation ‘Software testing is the process of executing software in a controlled manner, in order to answer the question: Does the software behave as specified. One way to ensure system‘s responsibility is to extensively test the system. Since software is a system component it requires a testing process also. / Software can be tested either manually or automatically. The two approaches are complementary: automated testing can perform a huge number of tests in short time or period, whereas manual testing uses the knowledge of the testing engineer to target testing to the parts of the system that are assumed to be more error-prone. Despite this contemporary, tools for manual and automatic testing are usually different, leading to decreased productivity and reliability of the testing process. Auto Test is a testing tool that provides a “best of both worlds” strategy: it integrates developers’ test cases into an automated process of systematic contractdriven testing. This allows it to combine the benefits of both approaches while keeping a simple interface, and to treat the two types of tests in a unified fashion: evaluation of results is the same, coverage measures are added up, and both types of tests can be saved in the same format. The objective of this paper is to discuss the Importance of Automation tool with associate to software testing techniques in software engineering. In this paper we provide introduction of software testing and describe the CASE tools. The solution of this problem leads to the new approach of software development known as software testing in the IT world. Software Test Automation is the process of automating the steps of manual test cases using an automation tool or utility to shorten the testing life cycle with respect to time.

<p>Over the next decade, it is estimated that the number of servers (virtual and physical) in enterprise datacenters will grow by a factor of 10, the amount of data managed by these datacenters will grow by a factor of 50, and the number of files the datacenter has to deal with will grow by a factor of 75. Meanwhile, skilled information technology (IT) staff to manage the growing number of servers and data will increase less than 1.5 times. Thus, a system administrator will face the challenging task of managing larger and larger numbers of production systems. We have developed solutions to make the system administrator more productive by automating some of the hard and time-consuming tasks in system management. In particular, we make new contributions in the Monitoring, Problem Diagnosing, and Testing phases of the system management cycle.</p><p>We start by describing our contributions in the Monitoring phase. We have developed a tool called Amulet that can continuously monitor and proactively detect problems on production systems. A notoriously hard problem that Amulet can detect is that of data corruption where bits of data in persistent storage differ from their true values. Once a problem is detected, our DiaDS tool helps in diagnosing the cause of the problem. DiaDS uses a novel combination of machine learning techniques and domain knowledge encoded in a symptoms database to guide the system administrator towards the root cause of the problem.</p><p>Before applying any change (e.g., changing a configuration parameter setting) to the production system, the system administrator needs to thoroughly understand the effect that this change can have. Well-meaning changes to production systems have led to performance or availability problems in the past. For this phase, our Flex tool enables administrators to evaluate the change hypothetically in a manner that is fairly accurate while avoiding overheads on the production system. We have conducted a comprehensive evaluation of Amulet, DiaDS, and Flex in terms of effectiveness, efficiency, integration of these contributions in the system management cycle, and how these tools bring data-intensive computing systems closer the goal of self-managing systems.</p> / Dissertation

Testing is a vital part of software development and test automation is an increasingly common practise. Performing automated testing on web-based applications is more complicated than desktop applications, which is particularly clear when it comes to testing a web based user interface as they are becoming more complex and dynamic. Depending on the goals and needed complexity of the testing, a variety of different frameworks/tools are available to help implementing it. This thesis investigates how automated testing of a web-based user interface can be implemented. Testing methods and a selection of relevant testing frameworks/tools are presented and evaluated based on given requirements. Out of the selected frameworks/tools, the Selenium WebDriver framework is chosen and used for implementation. The implementation results in automated test cases for regression testing of the functionality of a user interface created by Infor AB.

Telecom today has become an essence of life. Everywhere we see people using their smart phones for calling, checking email or accessing internet. To handle all these kinds of services without any intrusion is a very challenging task. This study deals with software testing which helps to ensure the quality of service to the end user. Software testing is an essential part in the software development process. Software development for telecom domain might not look as safety critical as of an airplane or nuclear reactor but it is arguably more complex. The main focus of this study is to provide automation to the unit testing of different types of radio connections that can be assigned to the end user based on the requested service and capacity of the 3G network. This research is sponsored by Ericsson to improve the testing of User Equipment Radio Connection Handling system that controls multiple possible radio connection configurations. This research attempts to identify and test all possible transitions between radio connection states. This will improve the existing manual state testing system, where changes in connection states cause dramatic impacts on test fixtures. As a solution, an automatic test case executor is proposed that generates possible transitions, which are later executed and verified automatically.

Due to the fast enlargement and complexity of systems used among telecommunication companies, the need for automatically testing has grown. The changeable nature of these systems makes implementation of automated testing to a difficult task. Finding an automated testing technique that is suitable for these types of systems is the subject of this thesis and several different types of scripting techniques has been considered. To be able to conduct this, an industrial case study is used; which shows how scripting techniques are affected by different types of changeability occurring in a system. / Marjaana Tienaho E-mail: Marjaana_tienaho@spray.se Jesús Barrio E-mail: jesus_barrio@hotmail.com E-mail: jesus_barrio@hotmail.com

Software test automation is widely accepted as an efficient software testing technique. However, automation has failed to deliver the expected productivity more often than not. The goal of this research was to find out the reason for these failures by collecting and understanding the metrics that affect software test automation and provide recommendations on how to successfully adopt automation with a positive return on investment (ROI). The metrics of concern were schedule, cost and effectiveness. The research employed an experimental study where subjects worked on individual manual and automated testing projects. The data collected were cross verified and supplemented with additional data from a feedback survey at the end of the experiment. The results of this study suggest that automation involves a heavy initial investment in terms of schedule and cost, which needs to be amortized over subsequent test cycles or even subsequent test projects.