• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 48
  • 9
  • 7
  • 6
  • 5
  • 2
  • 1
  • 1
  • Tagged with
  • 79
  • 79
  • 44
  • 32
  • 30
  • 25
  • 16
  • 15
  • 12
  • 12
  • 11
  • 10
  • 10
  • 10
  • 9
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

GUI test automation for Qt application

Wang, Lei January 2015 (has links)
GUI test automation is a popular and interesting subject in the testing industry. Many companies plan to start test automation projects in order to implement efficient, less expensive software testing. However, there are challenges for the testing team who lack experience performing GUI tests automation. Many GUI test automation projects have ended in failure due to mistakes made during the early stages of the project. The major work of this thesis is to find a solution to the challenges of establishing new test automation projects and determine an appropriate method to build GUI tests automation. Due to the particularity of GUI tests automation, keyword driven test approach is introduced in this thesis. The advantages and disadvantages are shown by undertaking comparison with the Record and replay testing method and the data driven testing method. The research also includes a feasibility study of GUI tests automation. The analysis report points out which kinds of test projects should be automated and which kinds should not be automated. Test automation tool selection is a critical step for an test automation project. This thesis shows the correct procedure for selecting a testing tool and explains the strategies of testing tool selection. It also summaries the mistakes made during the tool selection process. Several classical types of testing tools which support Qt software testing are compared and evaluated. Based on the in-depth analysis and comparison of testing tools, the thesis explains how the different tools fit with the different test projects. The implementation procedure of a test automation is demonstrated in this thesis. The procedure includes test case design and testing framework implementation. The test script is created based on the structure of a keyword driven test framework. The thesis also discusses several interesting topics related to GUI tests automation for future research.
2

Software test automation : a design and tool selection approach for a heterogeneous environment

Azrai, Iyad Shaher 23 April 2013 (has links)
This report describes a design approach for implementing a software test automation solution that can accommodate existing test processes in an organization. The process of implementing a software test automation solution is a large undertaking and requires careful planning to avoid unsuccessful implementations. This report outlines a design that can integrate with existing business and development processes in an organization, and recommends automation and development frameworks for achieving the test automation goals. Considerations for a heterogeneous test environment with varying types of supported operating systems, such as Windows and Linux, and multiple test execution environments, such as Java and .NET, have been made in this design and in the tool selections for the system implementation. The report also describes some of the challenges and caveats of automation in a heterogeneous environment along with recommended solutions to these challenges. / text
3

Investigating GUI test automation ROI : An industrial case study

Laurén, Rebecka January 2015 (has links)
This report is the proof of concept that shows how Coded UI can be used for the automation of GUI tests. For this thesis-work, an industrial case study is done on 26 different test cases provided at the company Basalt AB. The problem they had was that testing was very time consuming and was therefore not done as often as needed to keep the level of quality required for the system developed. The method that has been used are called the validation method and the work was according to that divided into five steps: choosing test cases, a learning process, implementation, compare the results and then draw conclusions. Test automation has benefits of time savings and the fact that tests will be reused. Testing will take minutes instead of hours and the tests can be executed over and over again as many times as needed. So by changing from manual testing to automated testing, tests can be run faster and therefore more often. The investment of automated testing will be repaid before the end of the fourth test round. So conclusions can be drawn from the results of this thesis and it shows that it absolutely is worth the investment of automating the testing process.
4

AUTOMATING VERIFICATION FOR LEGACY SYSTEMS: A CASE STUDY OF TECHNOLOGY SUSTAINMENT WITHIN THE NASA SPACE NETWORK

Irvin, Dana, Otranto, John, Lokshin, Kirill, Puri, Amit 10 1900 (has links)
The NASA Space Network (SN), which consists of the geosynchronous Tracking and Data Relay Satellite (TDRS) constellation and its associated ground elements, is a critical national space asset that provides near-continuous, high-bandwidth telemetry, command, and communications services for numerous spacecraft and launch vehicles. The Space Network includes several key ground system elements, one of which is the White Sands Complex Data Interface Service Capability (WDISC). The WDISC has undergone multiple cycles of modification and technology refresh over its lifetime, making test automation an attractive option for reducing system verification and validation cost. This paper considers the implementation of automated testing for the WDISC as a case study in technology sustainment, discusses the principal benefits and challenges of implementing test automation for a legacy system, and presents findings that demonstrate the effectiveness of such automation models.
5

TOWARDS FULLY AUTOMATED INSTRUMENTATION TEST SUPPORT

Jones, Charles H. 10 1900 (has links)
ITC/USA 2007 Conference Proceedings / The Forty-Third Annual International Telemetering Conference and Technical Exhibition / October 22-25, 2007 / Riviera Hotel & Convention Center, Las Vegas, Nevada / Imagine that a test vehicle has just arrived at your test facility and that it is fully instrumented with sensors and a data acquisition system (DAS). Imagine that a test engineer logs onto the vehicle’s DAS, submits a list of data requirements, and the DAS automatically configures itself to meet those data requirements. Imagine that the control room then contacts the DAS, downloads the configuration, and coordinates its own configuration with the vehicle’s setup. Imagine all of this done with no more human interaction than the original test engineer’s request. How close to this imaginary scenario is the instrumentation community? We’re not there yet, but through a variety of efforts, we are headed towards this fully automated scenario. This paper outlines the current status, current projects, and some missing pieces in the journey towards this end. This journey includes standards development in the Range Commander’s Council (RCC), smart sensor standards development through the Institute of Electrical and Electronics Engineers (IEEE), Small Business Innovation Research (SBIR) contracts, efforts by the integrated Network Enhanced Telemetry (iNET) project, and other projects involved in reaching this goal.
6

Application of a New Software Tool for the Automated Test of Automotive Electronic Control Unit Software

Amlinger, Hanna January 2009 (has links)
Testing plays a very important role for assuring the quality of developed software. In a modern vehicle, more and more of the functionality is controlled by software and the complexity of the software always increases. The expectations on automating the testing process are to save time and to reach an even higher quality. In this thesis, which was performed at ZF Friedrichshafen AG, a new tool for automated tests is studied. The tool is used for software in the loop simulation based system tests. The user specifies which outputs that shall be observed and which inputs that can be controlled. Based on these prerequisites, test cases are generated. It has been studied how to apply the tool, how the test case generation can be influenced, on which systems it successfully could be used and which results that could be reached with the tool. The tool has been evaluated on the hand of two real-life examples; the software of an automatic transmission and of a pressure controller, a module of this software. It was found that there are many interesting possibilities to apply the tool in order to support the present testing process.
7

Efficient And Maintainable Test Automation / Effektiv och underhållsbar testautomation

Ahmed, Abdifatah, Lindhe, Magnus January 2002 (has links)
More and more companies experience problems with maintainability and time-consuming development of automated testing tools. The MPC department at Ericsson Software Technology AB use methods and tools often developed during time pressure that results in time-consuming testing and requires more effort and resources than planned. The tools are also such nature that they are hard to expand, maintain and in some cases they have been thrown out between releases. For this reason, we could identify two major objectives that MPC want to achieve; efficient and maintainable test automation. Efficient test automation is related to mainly how to perform tests with less effort, or in a shorter time. Maintainable test automation aims to keep tests up to date with the software. In order to decide how to achieve these objectives, we decided to investigate which test to automate, what should be improved in the testing process, what techniques to use, and finally whether or not the use of automated testing can reduce the cost of testing. These issues will be discussed in this paper.
8

Automating a test strategy for a protocoldecoder tool

Johansson, Henrik January 2008 (has links)
Within Ericsson AB, integration and verification activities is done on the network level in order to secure the functionality of the network. Protocol analysers are used to capture the traffic in the network. This results in many log files, which needs to be analysed. To do this, a protocol decoder tool called Scapy/LHC is used. Scapy/LHC is a framework that allows the users to write their own script to retrieve the data they need from the log files. The Scapy/LHC framework is incrementally developed as open source within Ericsson when there are needs for more functionality. This is often done by the users, outside normal working tasks. Because of this, there is almost no testing done to verify that old and new functionality works as expected, and there is no formal test strategy in use today. <br />The goal of this master’s thesis is to evaluate test strategies that are possible to use on the Scapy/LHC framework. To make the time needed for the testing process as short as possible, the test strategy needs to be automated. Therefore, possible test automation tools shall also be evaluated. <br />Two possible test strategies and two possible test automation tools are evaluated in this thesis. A test strategy, where the scripts that are written by the users are used, is then selected for implementation. The two test automation tools are also implemented. The evaluation of the implemented test strategy shows that it is possible to find defects in the Scapy/LHC framework in a time efficient way with help of the implemented test strategy and any of the implemented test automation tools.
9

Automating a test method for a hybrid test environment

Eiderbrant, Tobias January 2010 (has links)
Ericsson has a very big and expensive test environment with a lot of GSM AXE equipment. In order to decrease the cost of testing Ericsson has developed a combination of simulated and real hardware, the Hybrid Test Environment (HTE). There is no formal supervision and testing of the HTE system today and this has left the HTE system unstable and the testers have been avoiding using HTE. It is important for Ericsson that the confidence for HTE will increase. The goal of this thesis is to produce a method for testing the HTE system. An automated test tool has been implemented in order to monitor and test the HTE system. During the two weeks that the test tool has been operational it has discovered 4 servers in 3 different HTE rigs that malfunctioned. These servers were fixed and were operational before the end-users could discover any problem.
10

Real-time auto-test monitoring system

Blixt, Fanny January 2021 (has links)
At Marginalen Bank, there are several microservices containing endpoints that are covered bytest automation. The documentation of which microservices and endpoints that are covered byautomated tests is currently done manually and is proven to contain mistakes. In the documentation, the test coverage for all microservices together and for every individual microserviceis presented. Marginalen Bank needs a way to automate this process with a system that cantake care of test coverage documentation and present the calculated data. Therefore, the purpose of this research is to find a way to create a real-time auto-test monitoring system thatautomatically detects and monitors microservices, endpoints, and test automation to documentand present test automation coverage on a website. The system is required to daily detect andupdate the documentation to be accurate and regularly find eventual changes. The implemented system that detects and documents the test automation coverage is calledTest Autobahn. For the system to detect all microservices, a custom hosted service was implemented that registers microservices. All microservices with the custom hosted service installedand extended to registers to Test Autobahn when deployed on a server. For the system todetect all endpoints of each microservice, a custom middleware was implemented that exposesall endpoints of a microservice with it installed. For the microservices to be able to install theseand get registered, a NuGet package containing the custom hosted service and the custom middleware, was created. To detect test automations, custom attributes models were created thatare supposed to be inserted into each test automation project. The custom attributes are placedin every test class and method within a project, to mark which microservice and endpoint thatis being tested within every automated test. The attributes of a project can be read throughthe assembly. To read the custom attributes within every test automation project, a consoleapplication, called Test Autobahn Automation Detector (TAAD), was implemented. TAADreads the assembly to detect the test automations and sends them to Test Autobahn. Test Autobahn couples the found test automation to the corresponding microservices and endpoints.TAAD is installed and ran on the build pipeline in Azure DevOps for each test automationproject to register the test automations. To daily detect and update the documentation of the test coverage, Quartz.NET hosted serviceis used. With Quartz.NET implemented, Test Autobahn can execute a specified job on a schedule. Within the job, Test Autobahn detects microservices and endpoints and calculates the testautomation coverage for the detection. The calculation of the test coverage from the latestdetection is presented on the webpage, containing both the test coverage for all microservicestogether and the test coverage for each microservice. According to the evaluations, the systemseems to function as anticipated, and the documentation is displaying the expected data.

Page generated in 0.1267 seconds