Relevant bibliographies by topics / GUI test

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'GUI test'

Author: Grafiati
Published: 4 June 2021
Last updated: 7 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'GUI test.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "GUI test"

1

Gandhi, G. Mohan Doss, and Anitha S. Pillai. "Challenges in GUI Test Automation." International Journal of Computer Theory and Engineering 6, no. 2 (2014): 192–95. http://dx.doi.org/10.7763/ijcte.2014.v6.860.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Gao, Zebao, Zhenyu Chen, Yunxiao Zou, and Atif M. Memon. "SITAR: GUI Test Script Repair." IEEE Transactions on Software Engineering 42, no. 2 (February 1, 2016): 170–86. http://dx.doi.org/10.1109/tse.2015.2454510.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Priya, G. Geetha, and B. Narendra Kumar Rao. "GUI Test Script Repair in Regression Testing." International Journal of Emerging Research in Management and Technology 6, no. 6 (June 29, 2018): 318. http://dx.doi.org/10.23956/ijermt.v6i6.289.

Full text
Abstract:
GUI testing is a process of testing a software application or functionality of GUI. It is defined as an interface between user and software which provides an easy way to interact with the system. GUI plays an important role in software engineering. GUI-based application requires that a test case consists of sequences of user actions/events to be executed. Selenium is an open-source tool for testing GUI Application by executing test cases whether the GUI Application is working properly or not. In this, we present test script repair technique to repair test cases. Test script repair technique uses reverse engineering process for creating the test script. Test script repair consists of three stages; they are Ripping, Mapping and Repairing. In ripping stage, there are two relationships for representing event interaction of GUI Application. During ripping we know the location of each widget. In mapping stage,original GUI events are mapped to an event-flow graph (EFG). In repairing stage, Event flow graph uses repairing transformations and human input to modified script to repair the test cases, and synthesizes a new “repaired” test script. During this process, test script repair uses GUI objects for yielding a final test script that can be executed using selenium tool to validate the GUI Application. An experiment using selenium tool to test, test cases suggests that it is effective in that unusable test scripts are repaired. Annotations significantly reduced the human cost to repair test cases.
APA, Harvard, Vancouver, ISO, and other styles
4

Fang, Xiaoxin, Bin Sheng, Ping Li, Dan Wu, and Enhua Wu. "Automatic GUI test by using SIFT matching." China Communications 13, no. 9 (September 2016): 227–36. http://dx.doi.org/10.1109/cc.2016.7582314.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mateo Navarro, Pedro Luis, Diego Sevilla Ruiz, and Gregorio Martínez Pérez. "A Proposal for Automatic Testing of GUIs Based on Annotated Use Cases." Advances in Software Engineering 2010 (November 5, 2010): 1–8. http://dx.doi.org/10.1155/2010/671284.

Full text
Abstract:
This paper presents a new approach to automatically generate GUI test cases and validation points from a set of annotated use cases. This technique helps to reduce the effort required in GUI modeling and test coverage analysis during the software testing process. The test case generation process described in this paper is initially guided by use cases describing the GUI behavior, recorded as a set of interactions with the GUI elements (e.g., widgets being clicked, data input, etc.). These use cases (modeled as a set of initial test cases) are annotated by the tester to indicate interesting variations in widget values (ranges, valid or invalid values) and validation rules with expected results. Once the use cases are annotated, this approach uses the new defined values and validation rules to automatically generate new test cases and validation points, easily expanding the test coverage. Also, the process allows narrowing the GUI model testing to precisely identify the set of GUI elements, interactions, and values the tester is interested in.
APA, Harvard, Vancouver, ISO, and other styles
6

Wan, Lin, and Qiu Ling Fan. "A Test Case Reuse Strategy on GUI Software." Applied Mechanics and Materials 543-547 (March 2014): 3339–42. http://dx.doi.org/10.4028/www.scientific.net/amm.543-547.3339.

Full text
Abstract:
The design of test cases plays an important role in GUI software testing. If test cases can be reused effectively, test time can be much reduced. Also, repetitive work can be avoided. Thus the efficiency of testing can be enhanced a lot. In this thesis, according to the characteristics of GUI software, a novel strategy of test cases reuse was proposed, which was proved efficient in practice.
APA, Harvard, Vancouver, ISO, and other styles
7

Tao, Chuanqi, and Jerry Gao. "Building a Model-Based GUI Test Automation System for Mobile Applications." International Journal of Software Engineering and Knowledge Engineering 26, no. 09n10 (November 2016): 1605–15. http://dx.doi.org/10.1142/s0218194016710042.

Full text
Abstract:
With the rapid advance of mobile computing technology and wireless networking, there is a significant increase of mobile applications (apps). This brings new business requirements and demands in mobile software testing, and causes new issues and challenges in mobile test automation. Existing mobile application testing approaches mostly concentrate on GUI-based testing, load and performance testing without considering large-scale concurrent mobile app test automation, and model-based test coverage analysis. In this paper, a mobile hierarchical GUI model is proposed to present mobile operation scenario flows and gesture features in a hierarchical manner, in order to facilitate test dependency analysis in test automation. Mobile app test coverage analysis is performed based on GUI ripping models. The paper also presents a developed system that provides a test automation solution using GUI models. Finally, the paper reports a case study to indicate the feasibility and effectiveness of the proposed approach.
APA, Harvard, Vancouver, ISO, and other styles
8

Ma, Yingzhe, and Eun-Man Choi. "Functional Test Automation for Android GUI Widgets Using XML." KIPS Transactions:PartD 19D, no. 2 (April 30, 2012): 203–10. http://dx.doi.org/10.3745/kipstd.2012.19d.2.203.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Maitrikul, C., and Y. Limpiyakorn. "GUI Test Case Prioritization using Social Network Analysis." Journal of Physics: Conference Series 1619 (August 2020): 012020. http://dx.doi.org/10.1088/1742-6596/1619/1/012020.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Tokgoz, Serkan, Yiya Hao, and Issa M. Panahi. "A hearing test simulator GUI for clinical testing." Journal of the Acoustical Society of America 143, no. 3 (March 2018): 1815. http://dx.doi.org/10.1121/1.5035952.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "GUI test"

1

Wang, Lei. "GUI test automation for Qt application." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-121719.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
2

Forslin, Sara. "Automatiska GUI-test : En teoretisk och praktisk studie för hållbarare test." Thesis, Uppsala universitet, Avdelningen för datorteknik, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-146754.

Full text
Abstract:
To automate software testing is an investment, and that makes it important to have good knowledge about automation before an implementation is made. In this master thesis a study about automated testing is carried out. The study also includes a closer look at the testing tool TestComplete. TestComplete is one out of many tools on the market that is developed for automated GUI testing and the goal is to get a picture of how well the tool can adjust to CC Systems own applications. Studies show that it is hard to write lasting test scripts. The automation must be implemented early in the development process and many protective measures have to be applied to the tests in order to protect  them. The report  also discusses a number of design requirements that is put on the tested application. These requirements are relatively easy to implement if they are known from the start of the development process. Two of the most important requirements are that the controls have to have specified names so the tests can use them and identify them and that the values that are important in the verification of the test have to be accessible and readable. CCSimTech is one of CC Systems own developed products and it is used in different hardware simulations. It is an important tool in manual testing at CC System today. Therefore it is important that also TestComplete can use it. To solve this, a library of functions adjusted for TestComplete has been created. The functions are developed so that they can be called directly from the test scripts in TestComplete in a user-friendly way. If the tests are able to call and use CCSimTech that will mean a way to further control the applications and make the test even more powerful
APA, Harvard, Vancouver, ISO, and other styles
3

Yuan, Xun. "Feedback-directed model-based GUI test case generation." College Park, Md.: University of Maryland, 2008. http://hdl.handle.net/1903/8621.

Full text
Abstract:
Thesis (Ph. D.) -- University of Maryland, College Park, 2008.
Thesis research directed by: Dept. of Computer Science. Title from t.p. of PDF. Includes bibliographical references. Published by UMI Dissertation Services, Ann Arbor, Mich. Also available in paper.
APA, Harvard, Vancouver, ISO, and other styles
4

GUILHON, RAQUEL JAUFFRET. "GUI TEST SUITE AUTOMATIC GENERATION FROM PETRI NET." PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2014. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=24513@1.

Full text
Abstract:
PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO
Na etapa de testes de software, as falhas podem ser reveladas e em seguida diagnosticadas a fim de identificar os defeitos que a causaram. Os testes devem idealmente ser aplicados desde o nível da unidade até o nível mais elevado do software, como o teste de sistema. Em um destes níveis está o teste da interface gráfica, ou Graphical User Interface (GUI). Garantir o correto funcionamento da GUI quanto ao estado de seus elementos após diversos eventos de usuário, é tão importante quanto o teste de outras camadas, pois a GUI é um meio direto de interação com a aplicação, sendo o recurso que mais influencia em como será qualificada a experiência pelo usuário final. Este trabalho propõe uma abordagem de teste baseado em modelo, ou Model-Based Testing (MBT), utilizando Redes de Petri (RP) de alto nível para representar a interface gráfica. A Rede de Petri é uma ferramenta de modelagem e uma linguagem de especificação de base matemática que define graficamente a estrutura de sistemas especialmente concorrentes. Uma característica importante das RPs é que elas podem ser simuladas, permitindo que se observe o comportamento do sistema e que se obtenha a geração de casos de teste a partir dos caminhos executados na simulação. Foi investigada a geração de suítes de teste para interface gráfica a partir do modelo Rede de Petri. Para isso, considerou-se a relação entre as ações do usuário e os estados resultantes na GUI, percebendo como uma RP pode modelá-los. Uma ferramenta de apoio foi desenvolvida para que, a partir das simulações realizadas na Rede de Petri, suítes de teste fossem geradas na linguagem C mais mais, tornando possível a execução automática em um software de estudo. Por fim, o critério de teste Análise de Mutantes, que mede a eficácia da suíte gerada a partir da RP, foi empregado como um dos meios de validação deste trabalho.
In software testing stage, faults can be revealed and then diagnosed to identify defects that caused it. Tests should ideally be applied from the unit level to the higher level of software, such as system testing. In one of these levels resides GUI (Graphical User Interface) testing. Ensuring the correct operation of the GUI on the state of its elements after various user events is as important as the other layers tests, since GUI is a direct way to interact with the application, being the feature that most influences how the experience will be qualified by the end user. This paper proposes a Model-Based Testing (MBT) approach using high-level Petri Nets (RP) to represent graphical user interface. Petri Net is a modeling tool and a mathematical specification language that graphically defines the structure of systems, specially the concurrent ones. An important feature of RPs is that they can be simulated, allowing one to observe the behavior of the system and to obtain the generation of test cases from the paths executed in the simulation. The generation of test suites for GUI from the Petri Net model was investigated. For this, we considered the relationship between user actions and resulting states in the GUI, realizing how an RP can model them. A support tool was developed so that, from the simulations of Petri Net, test suites were generated in C plus plus language, making it possible to auto-run them on a study software. Finally, the Mutation Analysis test criterion, which measures the effectiveness of the suite generated from RP, was employed as a means of validation of this work.
APA, Harvard, Vancouver, ISO, and other styles
5

Petersén, Elin. "Examining maintenance cost of automated GUI tests : An empirical study of how test script design affects the maintenance of automated visual GUI tests." Thesis, Linköpings universitet, Programvara och system, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-171783.

Full text
Abstract:
GUI testing is expensive to perform manually. Software systems involving a heterogeneous set of components exclude the applicability of specific GUI testing techniques. Visual GUI Testing (VGT) is a test automation technique that combines image recognition with scripts. It applies to almost any GUI driven application. VGT is proven to be cost-effective in comparison with manual testing. Still, it is expensive to maintain. This study investigates if test script design by following specific guidelines positively affects maintenance costs. A case study was conducted to identify best practices for VGT w.r.t. maintenance time. Four VGT versions were developed for each manual test case. These consisted of two design versions, with/without guidelines, for the two VGT-tools EyeAutomate and Sikuli. Data was collected using time measurements, observations, and interviews. Results highlighted differences in initial development time and maintenance time between the two design versions. In total, 44 observations were collected. 17 were related to the design versions, 17 to the VGT-tools, and 10 to VGT in general, initial development, and the system under test. The interviews collected the perceptions of VGT in general, maintenance of the different VGT versions, and guidelines. In conclusion, the combination of the guidelines did not have a positive effect on maintenance in terms of costs and experience. However, some of the individual guidelines did. A rationale why the guidelines did not give the desired result was identified. Future research is necessary to investigate other combinations of guidelines, such as those identified as beneficial.
APA, Harvard, Vancouver, ISO, and other styles
6

Laurén, Rebecka. "Investigating GUI test automation ROI : An industrial case study." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-28314.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
7

Lundin, Gustav. "Development of Graphical User Interface for the TSE test framework." Thesis, University West, Department of Technology, Mathematics and Computer Science, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:hv:diva-573.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Dahl, Thomas Eva, and Robin Borg. "Automatiserade GUI-tester i praktiken : En fallstudie på Triona AB." Thesis, Högskolan Dalarna, Informatik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:du-34255.

Full text
Abstract:
Testning är en nödvändig men kostsam del av mjukvaruutveckling. Test utförs på olika abstraktionsnivåer och kan vara manuella eller automatiserade. På lägsta abstraktionsnivå, enhetsnivå, är automatiserad testning vanligt och relativt okomplicerat, medan systemtester är svårare att automatisera. I synnerhet gäller detta tester på ett grafiskt användargränssnitt (GUI) som kräver speciella verktyg.   Triona vill undersöka möjligheterna att automatisera regressionstester från GUI:t av sin produkt C-Load, en molnbaserad webbtjänst för avtalsbaserad transportbokning.    Det primära syftet med denna fallstudie är att med en anpassad urvalsprocess utvärdera ett möjligt verktyg i förhållande till C-Load-förvaltningens förväntningar på automatiserad GUI testning (AGT) och att utifrån resultatet föreslå hur C-Loadförvaltningen kan gå vidare med val av verktyg för AGT. För att uppfylla syftet användes litteraturstudier, intervjuer och observationer av praktiska test.    Verktyg för GUI-testning kan delas in i tre huvudkategorier: skriptbaserade, modellbaserade och skriptlösa. Baserat på tidigare forskning drogs slutsatsen att ett skriptbaserat verktyg där koden i testskripten skrivs manuell bäst passar C-Loadförvaltningens krav och förutsättningar. Det mest använda verktyget av denna typ, Selenium WebDriver, utvärderades kvalitativt gentemot identifierade krav.    Av tidigare forskning framgår att vanliga utmaningar med skriptbaserade GUI-tester är att arbetsinsatsen för att skapa och underhålla testskript är stor och att testen kan vara opålitliga. Dessa problem framkom också i studiens intervjuer och observationer.   Slutsatsen är att det vore möjligt att automatisera regressionstester av C-Load med hjälp av Selenium Webdriver, och att det på sikt skulle kunna frigöra tid. Initialt krävs dock en omfattande insats för att implementera automatiserade tester i förvaltningen och Selenium Webdriver uppfyller bara delvis C-Load-förvaltningens förväntningar på AGT. C-Load-förvaltningen rekommenderas att utvärdera fler verktyg innan beslut fattas. I en kommande urvalsprocess bör Triona beakta hur väl olika verktyg fungerar i förhållande till moderna webbramverk.
Testing is a necessary but costly part of software development. Tests are performed at different abstraction levels and can be either manual or automated. On the lowest level of abstraction, where unit testing is performed, automated testing is commonplace and relatively uncomplicated, whereas system testing is more difficult to automate. This is especially true for GUI-testing, which requires special tools.      Triona wished to investigate possibilities to automate regression testing of the GUI for its C-load product, which is a Cloud-based web-service for contract-based transport booking.      The purpose of this case study was to evaluate one tool for automated GUI-testing (AGT) against the C-Load team’s expectations on AGT, and based on the result recommend Triona how to proceed in the process of implementing AGT. Literature studies, observations and interviews were conducted to fulfil the purpose.      GUI-testing tools can be classified into three categories: script-based, model-based and scriptless. One conclusion was that a script-based tool, where test scripts are manually coded would best suit Triona’s needs. The most used tool in that category, Selenium WebDriver, was tested and evaluated against requirements.       Prior research shows that common challenges encountered when using script-based GUItests are the workload required to create and maintain test scripts and that the tests can deliver inconsistent or “flaky” results. These challenges were confirmed during our analysis.       Our conclusion is that it is possible to automate C-Load regression tests with Selenium WebDriver, and that it would eventually free up time. However, a considerable effort is initially required to implement automated testing. Selenium Webdriver only partly fulfills the C-Load team’s expectations on AGT. Before a decision is taken, the C-Load team should evaluate more tools. When evaluating tools for AGT, Triona should take note that Selenium Webdriver can be deficient when it comes to testing applications based on modern web frameworks.
APA, Harvard, Vancouver, ISO, and other styles
9

Kurin, Erik, and Adam Melin. "Data-driven test automation : augmenting GUI testing in a web application." Thesis, Linköpings universitet, Programvara och system, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-96380.

Full text
Abstract:
For many companies today, it is highly valuable to collect and analyse data in order to support decision making and functions of various sorts. However, this kind of data-driven approach is seldomly applied to software testing and there is often a lack of verification that the testing performed is relevant to how the system under test is used. Therefore, the aim of this thesis is to investigate the possibility of introducing a data-driven approach to test automation by extracting user behaviour data and curating it to form input for testing. A prestudy was initially conducted in order to collect and assess different data sources for augmenting the testing. After suitable data sources were identified, the required data, including data about user activity in the system, was extracted. This data was then processed and three prototypes where built on top of this data. The first prototype augments the model-based testing by automatically creating models of the most common user behaviour by utilising data mining algorithms. The second prototype tests the most frequent occurring client actions. The last prototype visualises which features of the system are not covered by automated regression testing. The data extracted and analysed in this thesis facilitates the understanding of the behaviour of the users in the system under test. The three prototypes implemented with this data as their foundation can be used to assist other testing methods by visualising test coverage and executing regression tests.
APA, Harvard, Vancouver, ISO, and other styles
10

Polepalle, Chahna, and Ravi Shankar Kondoju. "Evidence and perceptions on GUI test automation : An explorative Multi-Case study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-15455.

Full text
Abstract:
Context. GUI-based automation testing is a costly and tedious activity in practice. As GUIs are well-known for being modified and redesigned throughout the development process, the corresponding test scripts are not valid anymore thereby being a hindrance to automation. Hence, substantial effort is invested in maintaining GUI test scripts which often leads to rework or waste due to improper decisions. As a result, practitioners have identified the need for decision support regarding when should GUI automation testing begin and how to make it easier and also identify what are the factors leading to waste in GUI-based automation testing. The current literature provides solutions relating to automation in general and few answers for GUI based-automation testing. Such generic answers might not be applicable to GUI test automation and also industries new to GUI development and testing. Thus, it is necessary to validate if the general solutions are applicable to GUI test automation and find additional answers that are not identified previously from practitioners opinions in an industrial context. Objectives. Capture relevant information regarding the current approach for GUI test automation within the subsystems from a case company. Next, identify the criteria for when to begin automation, testability requirements and factors associated with waste from literature and practice. Methods. We conducted a multiple-case study to explore opinions of practitioners in two subsystems at a Swedish telecommunication industry implementing GUI-automation testing. We conducted a literature review to identify answers from scientific literature prior to performing a case study.A two-phased interview was performed with different employees to collect their subjective opinions and also gather their opinions on the evidence collected from the literature. Later, Bayesian synthesis method was used to combine subjective opinions of practitioners with research-based evidence to produce context-specific results. Results. We identified 12 criteria for when to begin automation, 16 testability requirements and 15 factors associated with waste in GUI test automation.Each of them is classified into categories namely SUT-related,test-process related, test-tool related, human and organizational, environment and cross-cutting. New answers which were not present in the existing literature in the domain of the research are found. Conclusions. On validating the answers found in literature, it was revealed that the answers applicable for software test automation, in general, are valid for GUI automation testing as well. Since we incorporated subjective opinions to produce context specific results, we gained an understanding that every practitioner has their own way of working. Hence, this study aids in developing a common understanding to support informed subjective decisions based on evidence.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "GUI test"

1

Li, Kanglin. Effective GUI test automation: Developing an automated GUI testing tool. San Francisco, Calif: SYBEX, 2005.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Effective GUI test automation: Developing an automated GUI testing tool. San Francisco, Calif: SYBEX, 2005.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

She hui gui lü shu xing yu xing zheng wen ze shi jian jian yan: The attribute of social law and its empirical test in administrative accountability. Beijing Shi: She hui ke xue wen xian chu ban she, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Ce yan gai yao. [Beijing: Beijing zhong xian tuo fang ke ji fa zhan you xian gong si, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Casellato, Alessandro, ed. «Lavoro e conoscenza» dieci anni dopo. Florence: Firenze University Press, 2014. http://dx.doi.org/10.36253/978-88-6655-516-2.

Full text
Abstract:
Bruno Trentin, in occasione della laurea honoris causa conferitagli dall’ateneo in cui suo padre era stato un maestro prima che il fascismo lo costringesse all’esilio, tenne una lectio magistralis tesa e commossa. Dieci anni dopo, nello stesso luogo, studiosi di discipline e generazioni diverse rileggono quel testo e lo mettono in relazione con le proprie ricerche. Lavoro e conoscenza funziona come un prisma, da cui esce una gamma di colori ampia e variegata, che finisce per rivelare la complessa stratificazione di quella lezione che, infatti, condensa il pensiero e le speranze di uno degli intellettuali-politici più affascinanti del secondo ’900. Insieme agli atti del convegno questo libro raccoglie i testi della lectio trentiniana e della laudatio con cui gli fu tributata l’onorificenza.
APA, Harvard, Vancouver, ISO, and other styles
6

Caprettini, Gian Paolo. Segni, testi, comunicazione: Gli strumenti semiotici. Torino: UTET libreria, 1997.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Bastianini, Guido, Francesca Maltomini, and Gabriella Messeri, eds. Papiri della Società Italiana. Vol. XVI. Florence: Firenze University Press, 2013. http://dx.doi.org/10.36253/978-88-6655-383-0.

Full text
Abstract:
Questo volume XVI della serie dei PSI (avviata da Girolamo Vitelli nel 1912) contiene l’edizione di 79 testi in greco scritti su papiro o altro materiale (legno, pergamena) provenienti dall’Egitto e conservati all’Istituto Papirologico «G. Vitelli». Sono presenti sia frammenti di autori noti della letteratura greca (Omero, Esiodo, Erodoto, Tucidide, Senofonte, Isocrate, Demostene, Plutarco; i LXX, Cirillo di Alessandria, il Fisiologo), sia frammenti di opere sconosciute: si segnala fra gli altri un testo di grammatica sul dialetto ionico e un frammento dossografico sulla filosofia aristotelica. Vi sono poi testi di carattere documentario: petizioni, ricevute di tasse, registri, verbali, lettere private, testimonianza della vita quotidiana dell’Egitto di epoca romana e bizantina.
APA, Harvard, Vancouver, ISO, and other styles
8

Circumnavigare il testo: Gli indici in età moderna. Napoli: Liguori, 2009.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Pieri, Paolo Francesco. A partire da Jung: I testi e gli analisti. Milano: La biblioteca di Vivarium, 1998.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Perissinotto, Alessandro. Il testo multimediale: Gli ipertesti tra semiotica e didattica. Torino: UTET libreria, 2000.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "GUI test"

1

Bilke, Lars, Thomas Fischer, Dmitri Naumov, Daniel Pötschke, Karsten Rink, Amir Shoarian Sattari, Patrick Schmidt, Wenqing Wang, and Keita Yoshioka. "Code Descriptions." In GeomInt–Mechanical Integrity of Host Rocks, 243–54. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-61909-1_7.

Full text
Abstract:
AbstractThe FFS method (see Sect. 10.1007/978-3-030-61909-1_3) was developed to simulate direct shear tests. To provide a tool for the project work and get things easier done a graphical user interface (GUI) was also created. The GUI simply calls all necessary functions by letting the user either fill form fields or choose input files from the working folder. The rock parameters and the conditions of the direct shear test with the normal stress levels and shear displacements have to be selected. If an experiment is simulated the lab results can be selected as a text file so a visual comparison is possible. The geometry has to be loaded as a point cloud or an artificial surface can be generated. With small modifications the code can do multiple executions using artificial surfaces.
APA, Harvard, Vancouver, ISO, and other styles
2

Ha, Leegeun, Sungwon Kang, Jihyun Lee, and Younghun Han. "Automatic Generation of GUI Test Inputs Using User Configurations." In Big Data, Cloud Computing, Data Science & Engineering, 103–16. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-96803-2_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Chen, Tianxiang, Tao Song, Shusheng He, and Alei Liang. "A GUI-Based Automated Test System for Android Applications." In Advances in Intelligent Systems and Computing, 517–24. Singapore: Springer Singapore, 2018. http://dx.doi.org/10.1007/978-981-13-0344-9_44.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Jääskeläinen, Antti. "Towards Model Construction Based on Test Cases and GUI Extraction." In Testing Software and Systems, 225–30. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-47443-4_15.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Mauser, Daniel, Alexander Klaus, and Konstantin Holl. "Towards a GUI Test Model Using State Charts and Programming Code." In Testing Software and Systems, 271–76. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-41707-8_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Bauersfeld, Sebastian, Stefan Wappler, and Joachim Wegener. "A Metaheuristic Approach to Test Sequence Generation for Applications with a GUI." In Search Based Software Engineering, 173–87. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-23716-4_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Nurmuradov, Dmitry, Renée Bryce, Shraddha Piparia, and Barrett Bryant. "Clustering and Combinatorial Methods for Test Suite Prioritization of GUI and Web Applications." In Advances in Intelligent Systems and Computing, 459–66. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-77028-4_60.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Hubertz, Johannes. "GUI Tests." In Xpert.press, 183–222. Berlin, Heidelberg: Springer Berlin Heidelberg, 2016. http://dx.doi.org/10.1007/978-3-662-48603-0_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Arlt, Stephan, Pedro Borromeo, Martin Schäf, and Andreas Podelski. "Parameterized GUI Tests." In Testing Software and Systems, 247–62. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-34691-0_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Saha, Shaibal, and Supratic Chakraborty. "Development of GUI Based Test and Measurement Facilities for Studying Properties of MOS Devices in Clean Room Environment." In Lecture Notes in Electrical Engineering, 595–608. New York, NY: Springer New York, 2012. http://dx.doi.org/10.1007/978-1-4614-3535-8_50.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "GUI test"

1

Murthy, PVR, and Andreas Ulrich. "Distributed GUI Test Automation." In 2017 14th IEEE India Council International Conference (INDICON). IEEE, 2017. http://dx.doi.org/10.1109/indicon.2017.8487560.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Lu, Lu, and Ying Huang. "Automated GUI Test Case Generation." In 2012 International Conference on Computer Science and Service System (CSSS). IEEE, 2012. http://dx.doi.org/10.1109/csss.2012.151.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Zhu, Xiaochun, Bo Zhou, Juefeng Li, and Qiu Gao. "A test automation solution on GUI functional test." In 2008 6th IEEE International Conference on Industrial Informatics (INDIN). IEEE, 2008. http://dx.doi.org/10.1109/indin.2008.4618325.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Yandrapally, Rahulkrishna, Giriprasad Sridhara, and Saurabh Sinha. "Automated Modularization of GUI Test Cases." In 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering (ICSE). IEEE, 2015. http://dx.doi.org/10.1109/icse.2015.27.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Yuan, Xun, and Atif M. Memon. "Alternating GUI Test Generation and Execution." In Industrial Conference - Practice and Research Techniques (TAIC PART). IEEE, 2008. http://dx.doi.org/10.1109/taic-part.2008.10.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Cheng, Lin, Zijiang Yang, and Chao Wang. "Systematic reduction of GUI test sequences." In 2017 32nd IEEE/ACM International Conference on Automated Software Engineering (ASE). IEEE, 2017. http://dx.doi.org/10.1109/ase.2017.8115696.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Zhao, Lei, and Kai-Yuan Cai. "On Modeling of GUI Test Profile." In 2010 IEEE International Conference on Software Testing Verification and Validation Workshop (ICSTW). IEEE, 2010. http://dx.doi.org/10.1109/icstw.2010.19.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Devaki, Pranavadatta, Suresh Thummalapenta, Nimit Singhania, and Saurabh Sinha. "Efficient and flexible GUI test execution via test merging." In ISSTA '13: Iitsnternational Symposium on Software Testing and Analysis. New York, NY, USA: ACM, 2013. http://dx.doi.org/10.1145/2483760.2483781.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Nguyen, Duc Hoai, Paul Strooper, and Jorn Guy Suess. "Model-based testing of multiple GUI variants using the GUI test generator." In the 5th Workshop. New York, New York, USA: ACM Press, 2010. http://dx.doi.org/10.1145/1808266.1808270.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Daniel, Brett, Qingzhou Luo, Mehdi Mirzaaghaei, Danny Dig, Darko Marinov, and Mauro Pezzè. "Automated GUI refactoring and test script repair." In the First International Workshop. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/2002931.2002937.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "GUI test"

1

Schoen, Roberta, Clara Gannon, Maureen Malone, Phyllis Levine, Marjorie Powell, Wendy Hill, Rick Wayman, and Tammy Borkowski. Defense Research, Development, Test, and Evaluation (RDT&E) Online System (DROLS) Replacement Graphical User Interface (GUI) Design Group. Fort Belvoir, VA: Defense Technical Information Center, July 1998. http://dx.doi.org/10.21236/ada370718.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Carleton, J. J. II, L. Fox, and C. R. Rudy. Air gun test evaluation. Office of Scientific and Technical Information (OSTI), January 1992. http://dx.doi.org/10.2172/5707011.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

MISSILE DEFENSE AGENCY WASHINGTON DC. Vertical Gun Test Environmental Assessment. Fort Belvoir, VA: Defense Technical Information Center, May 2004. http://dx.doi.org/10.21236/ada515771.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Trim, M., Matthew Murray, and C. Crane. Modernization and structural evaluation of the improved Overhead Cable System. Engineer Research and Development Center (U.S.), March 2021. http://dx.doi.org/10.21079/11681/40025.

Full text
Abstract:
A modernized Overhead Cable System prototype for a 689 ft (210 m) Improved Ribbon Bridge crossing was designed, assembled, and structurally tested. Two independent structural tests were executed, i.e., a component-level compression test of the BSS tower was performed to determine its load capacity and failure mode; and a system-level ‘dry’ test of the improved OCS prototype was conducted to determine the limit state and failure mode of the entire OCS. In the component-level compression test of the BSS tower, the compressive capacity was determined to be 102 kips, and the failure mode was localized buckling in the legs of the tower section. During system-level testing, the prototype performed well up to 40.5 kips of simulated drag load, which corresponds to a uniformly distributed current velocity of 10.7 ft/s. If a more realistic, less conservative parabolic velocity distribution is assumed instead, the drag load for an 11 ft/s current is 21.1 kips. Under this assumption, the improved OCS prototype has a factor of safety of 1.9, based on a 689-ft crossing and 11-ft/s current. The OCS failed when one of the tower guy wires pulled out of the ground, causing the tower to overturn.
APA, Harvard, Vancouver, ISO, and other styles
5

WALKER, PAMELA K., and PHILIP J. RODACY. Field Test Kit for Gun Residue Detection. Office of Scientific and Technical Information (OSTI), January 2002. http://dx.doi.org/10.2172/792870.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Harrier, Danielle. Cylinder expansion test and gas gun experiment comparison. Office of Scientific and Technical Information (OSTI), June 2016. http://dx.doi.org/10.2172/1261800.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Pikin A., I. Ben-Zvi, X. Y. Chang, D. Gassner, V. Litvinenko, O. Rahman, T. Rao, et al. Depressed electron collector for the Gatling Gun Test Stand. Office of Scientific and Technical Information (OSTI), October 2013. http://dx.doi.org/10.2172/1104830.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Gierman, S. M. Cold Test Measurements on the GTF Prototype RF Gun. Office of Scientific and Technical Information (OSTI), December 2010. http://dx.doi.org/10.2172/993721.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Gierman, S. M. Cold Test Measurements on the GTF Prototype RF Gun. Office of Scientific and Technical Information (OSTI), November 2010. http://dx.doi.org/10.2172/993731.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Parsa, Z., and L. Young. Brookhaven Accelerator Test Facility photocathode gun and transport beamline. Office of Scientific and Technical Information (OSTI), January 1990. http://dx.doi.org/10.2172/6778458.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'GUI test' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography