Thematische Bibliographien / Testing

Inhaltsverzeichnis

  1. Zeitschriftenartikel
  2. Dissertationen
  3. Bücher
  4. Buchteile
  5. Konferenzberichte
  6. Berichte der Organisationen

Auswahl der wissenschaftlichen Literatur zum Thema „Testing“

Autor: Grafiati
Veröffentlicht am 4. Juni 2021
Zuletzt aktualisiert am 9. Juni 2025

Geben Sie eine Quelle nach APA, MLA, Chicago, Harvard und anderen Zitierweisen an

Wählen Sie eine Art der Quelle aus:

Machen Sie sich mit den Listen der aktuellen Artikel, Bücher, Dissertationen, Berichten und anderer wissenschaftlichen Quellen zum Thema "Testing" bekannt.

Neben jedem Werk im Literaturverzeichnis ist die Option "Zur Bibliographie hinzufügen" verfügbar. Nutzen Sie sie, wird Ihre bibliographische Angabe des gewählten Werkes nach der nötigen Zitierweise (APA, MLA, Harvard, Chicago, Vancouver usw.) automatisch gestaltet.

Sie können auch den vollen Text der wissenschaftlichen Publikation im PDF-Format herunterladen und eine Online-Annotation der Arbeit lesen, wenn die relevanten Parameter in den Metadaten verfügbar sind.

Zeitschriftenartikel zum Thema "Testing"

1

Praveen, Kumar Koppanati. "Parallelizing Automated UI and API Tests for Java Applications." Journal of Scientific and Engineering Research 10, no. 3 (March 31, 2023): 155–59. https://doi.org/10.5281/zenodo.13912400.

Der volle Inhalt der Quelle
Annotation:
The growth and complexity of modern Java applications require newer testing strategies to make it efficient and faster. Automated testing, both for User Interfaces (UI) and Application Programming Interfaces (APIs), is crucial in maintaining the reliability and robustness of these applications. However, traditional approaches to automated testing often involve sequential execution, which can lead to significant delays in feedback and increased time-to-market. This paper discusses the parallelization of automated UI and API tests for Java applications to improve performance and testing efficiency. Leveraging the inherent concurrency of modern hardware and distributed systems, we explore techniques for parallel test execution, examining frameworks such as Selenium, TestNG, and JUnit. By implementing parallelization strategies, organizations can significantly reduce test execution times, enhance resource utilization, and improve the overall quality of software delivery. Additionally, we discuss the potential challenges, including test dependencies, data management, and synchronization issues, and provide solutions to address these concerns.
APA, Harvard, Vancouver, ISO und andere Zitierweisen
2

Seth, Jyotsna, Mukul Varshney, and Shivani Garg Abha Kiran Rajpoot. "Automated Testing: An Edge Over Manual Software Testing." International Journal of Trend in Scientific Research and Development Volume-1, Issue-4 (June 30, 2017): 710–13. http://dx.doi.org/10.31142/ijtsrd2232.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
3

Brower, Vicki. "Testing, testing … testing?" Nature Medicine 3, no. 2 (February 1997): 131–32. http://dx.doi.org/10.1038/nm0297-131.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
4

Putterman, Chaim, and Eldad Ben-Chetrit. "Testing, Testing, Testing . . ." New England Journal of Medicine 333, no. 18 (November 2, 1995): 1208–11. http://dx.doi.org/10.1056/nejm199511023331809.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
5

Petro, Jane A. "Testing, Testing, Testing." American Journal of Cosmetic Surgery 32, no. 2 (June 2015): 43–46. http://dx.doi.org/10.1177/074880681503200201.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
6

Petro, Jane A. "Testing, Testing, Testing." American Journal of Cosmetic Surgery 32, no. 2 (June 2015): 43–46. http://dx.doi.org/10.5992/0748-8068-32.2.43.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
7

Rogers, Tim B. "Testing Testing Testing..." Theory & Psychology 4, no. 2 (May 1994): 300–302. http://dx.doi.org/10.1177/0959354394042016.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
8

Chandrasekhar, K. "Testing Web Application using Selenium Testing Tool with Respect to Test’ng." International Journal for Research in Applied Science and Engineering Technology 6, no. 4 (April 30, 2018): 4766–70. http://dx.doi.org/10.22214/ijraset.2018.4781.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
9

Bashir, Josefeena. "Hypothesis Testing." Scientific Journal of India 3, no. 1 (December 31, 2018): 62–63. http://dx.doi.org/10.21276/24565644/2018.v3.i1.21.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
10

Gallagher, C. "'Testing, testing' [product testing]." Manufacturing Engineer 81, no. 6 (December 1, 2002): 249–52. http://dx.doi.org/10.1049/me:20020601.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
Mehr Quellen

Dissertationen zum Thema "Testing"

1

Tipler, Bradley Thomas Carleton University Dissertation Engineering Electrical. "Testify; an environment for automated testing." Ottawa, 1987.

Den vollen Inhalt der Quelle finden
APA, Harvard, Vancouver, ISO und andere Zitierweisen
2

Oftedal, Kristian. "Random Testing versus Partition Testing." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-13985.

Der volle Inhalt der Quelle
Annotation:
The difference between Partition Testing and Random Testing has been thoroughlyinvestigated theoretically. In this thesis we present a practical study ofthe differences between random testing and partition testing. Thestudy is performed on the open-source project Buddi with JUnit and Randoop as test tools. The comparisonis made with respect to coverage rate and fault rate. The resultsare discussed and analyzed. The observed differences are statisticallysignificant at the 10% level with respect to coverage rate, in favour ofpartition testing, and not statistically significant at the 10% level withrespect to the fault rate.
APA, Harvard, Vancouver, ISO und andere Zitierweisen
3

Shah, Syed Muhammad Ali, and Usman Sattar Alvi. "A Mix Testing Process Integrating Two Manual Testing Approaches : Exploratory Testing and Test Case Based Testing." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3083.

Der volle Inhalt der Quelle
Annotation:
Software testing is a key phase in software development lifecycle. Testing objectives corresponds to the discovery and detection of faults, which can be attained by utilizing manual or automated testing approaches. In this thesis, we are mainly concerned with the manual test approaches. The most commonly used manual testing approaches in the software industry are the Exploratory Testing (ET) approach and the Test Case Based Testing (TCBT) approach. TCBT is primarily used by software testers to formulize and guide their testing tasks and set the theoretical principles for testing. On the other hand ET is simultaneous learning, test design, and test execution. Software testing might benefit from an intelligent combination of these approaches of testing however there is no proof of any formal process that accommodates the usage of both test approaches in a combination. This thesis presents a process for Mix Testing (MT) based on the strengths and weaknesses of both test approaches, identified through a systematic literature review and interviews with testers in a software organization. The new process is defined through the mapping of weaknesses of one approach to the strengths of other. Static validation of the MT process through interviews in the software organization suggested that MT has ability to resolve the problems of both test approaches to some extent. Furthermore, MT was validated by conducting an experiment in an industrial setting. The analysis of the experimentation results indicated that MT has better defect detection than TCBT and less than ET. In addition, the results of the experiments also indicate that MT provides equal functionality coverage as compared to ET and TCBT.
APA, Harvard, Vancouver, ISO und andere Zitierweisen
4

Медведєва, С. О., and О. А. Абдуллаєв. "Testing. Basic concepts of testing software." Thesis, ВНТУ, 2019. http://ir.lib.vntu.edu.ua//handle/123456789/24789.

Der volle Inhalt der Quelle
Annotation:
У даній доповіді розглянуто основні концепції та види тестування програмного забезпечення, а також окреслено важливість приділення йому великої уваги у інших сферах.<br>This paper examines the basic concepts and methods of software testing, and highlights the importance of paying attention to testing in other areas
APA, Harvard, Vancouver, ISO und andere Zitierweisen
5

El-Fakih, Khaled Abdul-Ghani. "Protocol re-testing and diagnostic testing methods." Thesis, University of Ottawa (Canada), 2002. http://hdl.handle.net/10393/6429.

Der volle Inhalt der Quelle
Annotation:
Many test selection methods have been developed for deriving tests when a system specification is represented in the form of a Finite State Machine (FSM). In the first part of this thesis, we present test generation methods that select tests for testing the modified parts of the system specification, in order to check that these modifications were correctly implemented in the system implementation. These methods are based on well-known test derivation methods called the W, Wp, HIS and distinguishing sequence methods. As the purpose of conformance testing is to check whether an implementation conforms to its specification, an interesting complementary problem is to locate the differences between a specification and its implementation when the implementation is found to be nonconforming. In the second part of this thesis, we consider a system consisting of two communicating FSMs, called components. First, we show that it is not always possible to locate a fault within the given system, once a fault has been detected in its implementation (called System Under Test (SUT)). Accordingly, we present two new two-level approaches for fault localization within the given system. The first method assumes that the SUT has a single fault in one of its components. Consequently, at the first diagnostic level the methods decide whether it is possible to identify the faulty component in the given system. If this is possible, the faulty component is identified, and if desired, at the second level, the methods determine whether it is possible to locate the fault within the faulty component. If that is possible, the methods provide additional test cases to locate the fault. The second method considers the case when the SUT may have multiple faults in at most one of its components. At the machine level diagnosis, the method decides whether it is possible to identify the faulty component machine in the given system, once faults have been detected in a system implementation. If this is possible, it provides tests for identifying the faulty component machine, and if desired, the method can be used to determine whether it is possible to locate the faults within the faulty component. If that is possible, he method provides additional test cases to locate the faults. (Abstract shortened by UMI.)
APA, Harvard, Vancouver, ISO und andere Zitierweisen
6

Myllylahti, J. (Juho). "Incorporating fuzz testing to unit testing regime." Master's thesis, University of Oulu, 2014. http://urn.fi/URN:NBN:fi:oulu-201311211914.

Der volle Inhalt der Quelle
Annotation:
Software defects are a common problem, despite of decades of research on how to seek and destroy bugs. Software defects are not a mere nuisance, since they come with a very real cost to the industry and the users of software, leading to loss of millions of dollars, countless hours of work and even human lives. Thus there is a very real need to invent new ways to hunt down software defects. This thesis aims to answer questions concerning integration of modern software development pipeline and fuzzing, an effective fault-based testing technique with strong background in security and robustness testing. More specifically, this thesis seeks to find out how to integrate fuzz testing with continuous integration frameworks to lessen the redundancy in testing: fuzzing usually has its own, separate testing pipeline. Additionally this thesis looks into the possibility of automating generation of fuzzed unit tests using a tool that would use existing unit tests as the raw material for creating the tests to determine, if such approach could be feasible. This study consists of theoretical and empirical parts. The literature part explores software testing research for results relevant to this thesis, empirical part describes a prototype of unit test fuzzer developed for unit tests written in Python, and observations of relevant issues made during the development process while also describing experiences of how well test cases generated by the tool or manually could be introduced to the existing continuous integration workflow. Research method applied is design science. The findings show that creating the tool described is not as easy as it would first seem, listing issues large enough to motivate discontinuing the prototyping after first initial version. On the other hand, integrating fuzzing to a continuous integration based workflow seems to be a feasible idea, and automated test case generation is not the only way to create fault-based unit tests.
APA, Harvard, Vancouver, ISO und andere Zitierweisen
7

Polamreddy, Rakesh Reddy, and Syed Ail Irtaza. "Software Testing : A Comparative Study Model Based Testing VS Test Case Based Testing." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3498.

Der volle Inhalt der Quelle
Annotation:
Software testing is considered as one of the key phases in the software-development life cycle (SDLC). The main objective of software testing is to detect the faults either through manual testing or with automated testing approach. The most commonly adopted software testing approach in industries is test case based testing (TCBT) which is usually done manually. TCBT is mainly used by the software testers to formalize and guide their testing activities and set theoretical principals for testing. On the other hand, model based testing (MBT) is widely used automation software testing technique to generate and execute the tests. Both techniques are showing their prominence in real time with some pros and cons. However, there is no formal comparison available between these two techniques. The main objective of this thesis work is to find out the difference in test cases in TCBT and MBT in terms of providing better test coverage ( Statement, Branch and Path), requirement traceability, cost and time. To fulfill the aims of the research we have conducted interviews for static validation, and later we did an experiment for validating those results dynamically. The analysis of experiment results showed that the requirement traceability in MBT generated test cases are very hard to make the test cases traceable to the requirements, particularly with the open-source tool Model J-Unit. However, this can be done by using other commercial tools like Microsoft Spec Explorer or Conformiq Qtronic. Furthermore, we found by conducting experiment, that MBT consumes less time thus it is cost-effective as compared to TCBT and also MBT show better test coverage than TCBT. Moreover, we found that, in our case, requirement traceability is better in traditional TCBT approach as compared to MBT.<br>+4746851975
APA, Harvard, Vancouver, ISO und andere Zitierweisen
8

Michaels, Ryan P. "Combinatorial-Based Testing Strategies for Mobile Application Testing." Thesis, University of North Texas, 2020. https://digital.library.unt.edu/ark:/67531/metadc1752354/.

Der volle Inhalt der Quelle
Annotation:
This work introduces three new coverage criteria based on combinatorial-based event and element sequences that occur in the mobile environment. The novel combinatorial-based criteria are used to reduce, prioritize, and generate test suites for mobile applications. The combinatorial-based criteria include unique coverage of events and elements with different respects to ordering. For instance, consider the coverage of a pair of events, e1 and e2. The least strict criterion, Combinatorial Coverage (CCov), counts the combination of these two events in a test case without respect to the order in which the events occur. That is, the combination (e1, e2) is the same as (e2, e1). The second criterion, Sequence-Based Combinatorial Coverage (SCov), considers the order of occurrence within a test case. Sequences (e1, ..., e2) and (e2,..., e1) are different sequences. The third and strictest criterion is Consecutive-Sequence Combinatorial Coverage (CSCov), which counts adjacent sequences of consecutive pairs. The sequence (e1, e2) is only counted if e1 immediately occurs before e2. The first contribution uses the novel combinatorial-based criteria for the purpose of test suite reduction. Empirical studies reveal that the criteria, when used with event sequences and sequences of size t=2, reduce the test suites by 22.8%-61.3% while the reduced test suites provide 98.8% to 100% fault finding effectiveness. Empirical studies in Android also reveal that the event sequence criteria of size t=2 reduce the test suites by 24.67%-66% while losing at most 0.39% code coverage. When the criteria are used with element sequences and sequences of size t=2, the test suites are reduced by 40\% to 72.67%, losing less than 0.87% code coverage. The second contribution of this work applies the combinatorial-based criteria for test suite prioritization of mobile application test suites. The results of an empirical study show that the prioritization criteria that use element and event sequences cover the test suite's elements, events, and code faster than random orderings. On average the prioritized orderings cover all elements within 21.81% of the test suite, all events within 45.99% of the test suite, and all code within 51.21% of the test suite. Random orderings achieve full code coverage with 84.8% of the test suite on average. The third contribution uses the combinatorial-based criteria for test suite generation. This work modifies the random walk tool used from prior experiments to give weight (preference) to coverage of the combinatorial-based event and element criteria. The use of Element SCov and CSCov criteria result in test suites that increase code coverage for three of the four subject applications. Specifically, the code coverage increases by 0.29%-5.89% with SCov and 1.36%-6.79% with CSCov in comparison to the original random walk algorithm. The SCov criterion increases total sequence coverage by 5%-88% and the CSCov criterion increases sequence coverage by 13%-68%. One criteria, Element CCov, failed to increase code coverage for two of the four applications. The contributions of this dissertation show that the novel combinatorial-based criteria using sequences of events and elements offer improvements to different testing strategies for mobile applications, including test suite reduction, prioritization, and generation.
APA, Harvard, Vancouver, ISO und andere Zitierweisen
9

Borg, Daniel, and Anders Elfström. "Automatiserad testning av användargränssnitt i SharePoint : Automated UI Testing in SharePoint." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-177132.

Der volle Inhalt der Quelle
Annotation:
Företag arbetar ofta efter hårda krav från kunder där lösningar måste levereras på ett tidseffektivt sätt och samtidigt hålla en hög kvalitet. Detta i form av felfria och robusta system vilket delvis kan åstadkommas med hjälp av testning. Kraven på snabb leverans och hög kvalitet är däremot motpoler till varandra; snabb leverans genomförs ofta på bekostnad av kvalitet och tvärtom. Agila arbetsmetoder med tidiga och frekventa leveranser har ändrat på detta, men kräver samtidigt en ständig kvalitetsförsäkring under arbetets löptid. Under utveckling av mjukvara enligt dessa metoder förekommer därför en kontinuerlig kvalitetssäkringsprocess för att säkerställa att produkten dels uppfyller vad kravspecifikationen avser samt att levererad produkt håller en hög tekniskt kvalitet i form av buggfri och robust kod som innehar stor pålitlighet för framtiden. Då manuell testning är en kostnad- och resurskrävande metod har automatiserad testning blivit ett aktuellt alternativ för ökad effektivitet och hållbar utveckling. Målet med det här arbetet har varit att för Precio Systemutveckling AB utreda möjligheterna för en implementation av automatiserad testning av användargränssnitt, i en hos företaget redan existerande och etablerad utvecklingsprocess. Arbetet har genomförts med en inledande förstudie om testning med fokus på varför det är en extra viktig faktor i dagsläget. Detta följs av ett avsnitt där existerande teori och teknik för testning i generell mening avhandlats, följt av en närmare studie på hur automatiserad testning är rekommenderad att utföras ur ett perspektiv från utveckling av produkter inom Microsoft-teknologi.<br>Software companies work under a strict pressure from customers where solutions must be delivered in a timely manner as well as providing high quality and value. The products should be robust and without errors, which partially can be accomplished by testing during the development process. The requirement for an early delivery and a high quality does not always come hand in hand, but with the increased use of agile software development methods, this can be achieved. During agile development of software, there is a continuous process to ensure the quality of what is being developed, both to make sure that all the functional requirements are fulfilled, but also that the code behind is robust and dependable for the future. Since manual testing can be both time and resource consuming, automated testing has become a modern alternative to increase productivity and to maintain a sustainable development process. The goal of this thesis work has been to investigate the possibilities of implementing a solution for automated UI testing in an already existing development process at the company Precio Systemutveckling AB. The work has been conducted in three steps, starting with a literature study about testing in general, followed by an extensive research into suitable tools and technology for testing that exists today. After this, a deeper look was made at what the recommended solutions for implementing automated testing in a Microsoft-oriented enviroment were. The work was concluded with an actual implementation of automated testing on premise at Precio.
APA, Harvard, Vancouver, ISO und andere Zitierweisen
10

Ho, Kam Seng. "Workflow testing." Thesis, University of Macau, 2011. http://umaclib3.umac.mo/record=b2550562.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
Mehr Quellen

Bücher zum Thema "Testing"

1

Edlich, Stefan. Next generation testing mit TestNG & Co. [Frankfurt (Main)]: Entwickler.press, 2007.

Den vollen Inhalt der Quelle finden
APA, Harvard, Vancouver, ISO und andere Zitierweisen
2

E, Held Robin, ed. Testing. Seattle: Marquand Books, 2004.

Den vollen Inhalt der Quelle finden
APA, Harvard, Vancouver, ISO und andere Zitierweisen
3

(Firm), Bantam Books, and Copyright Paperback Collection (Library of Congress), eds. Testing. New York: Bantam Books, 1993.

Den vollen Inhalt der Quelle finden
APA, Harvard, Vancouver, ISO und andere Zitierweisen
4

Lachapelle, Jean-Marie, and Howard I. Maibach, eds. Patch Testing and Prick Testing. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-27099-5.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
5

Lachapelle, Jean-Marie, and Howard I. Maibach. Patch Testing and Prick Testing. Berlin, Heidelberg: Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-25492-5.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
6

Lachapelle, Jean-Marie, and Howard I. Maibach. Patch Testing and Prick Testing. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-662-09215-6.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
7

Beust, Cédric. Next generation Java testing: TestNG and advanced concepts. Upper Saddle River, NJ: Addison-Wesley, 2008.

Den vollen Inhalt der Quelle finden
APA, Harvard, Vancouver, ISO und andere Zitierweisen
8

W, Anderson B. Gem testing. London [England]: Butterworths, 1990.

Den vollen Inhalt der Quelle finden
APA, Harvard, Vancouver, ISO und andere Zitierweisen
9

R, Ericsson Neil, ed. Testing exogeneity. Oxford: Oxford University Press, 1995.

Den vollen Inhalt der Quelle finden
APA, Harvard, Vancouver, ISO und andere Zitierweisen
10

Grellmann, Wolfgang, and Sabine Seidler, eds. Polymer Testing. München: Carl Hanser Verlag GmbH & Co. KG, 2007. http://dx.doi.org/10.3139/9783446433595.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
Mehr Quellen

Buchteile zum Thema "Testing"

1

Holcombe, Mike, and Florentin Ipate. "Testing, Testing, Testing!" In Correct Systems, 61–92. London: Springer London, 1998. http://dx.doi.org/10.1007/978-1-4471-3435-0_3.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
2

Davies, Rebekah. "Testing, Testing." In Navigating Telehealth for Speech and Language Therapists, 52. London: Routledge, 2022. http://dx.doi.org/10.4324/9781003269724-15.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
3

Frasca, Tim. "Peru: Testing, Testing." In AIDS in Latin America, 33–70. New York: Palgrave Macmillan US, 2005. http://dx.doi.org/10.1057/9781403979087_2.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
4

Hai-Jew, Shalin. "Alpha Testing, Beta Testing, and Customized Testing." In Designing Instruction For Open Sharing, 381–428. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-030-02713-1_9.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
5

Bradburne, Alan. "Testing." In Rails 5 Revealed, 35–42. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1709-2_4.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
6

Maskrey, Molly K. "Testing." In App Development Recipes for iOS and watchOS, 301–49. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1820-4_12.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
7

Lawrenz, Wolfhard, Federico Cañas, Maria Fischer, Stefan Krauß, Lothar Kukla, and Nils Obermoeller. "Testing." In CAN System Engineering, 283–343. London: Springer London, 2013. http://dx.doi.org/10.1007/978-1-4471-5613-0_6.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
8

Czichos, Horst. "Testing." In Measurement, Testing and Sensor Technology, 25–42. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-76385-9_2.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
9

Rudd, Anthony S. "Testing." In Implementing Practical DB2 Applications, 164–70. London: Springer London, 1996. http://dx.doi.org/10.1007/978-1-4471-1035-4_10.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
10

Lunn, Ken. "Testing." In Software Development with UML, 309–28. London: Macmillan Education UK, 2003. http://dx.doi.org/10.1007/978-0-230-80419-7_17.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen

Konferenzberichte zum Thema "Testing"

1

Sobaru, F. "Immunity Testing." In 2006_EMC-Europe_Barcelona, 1–15. IEEE, 2006. https://doi.org/10.23919/emc.2006.10813189.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
2

Himmler, Andreas. "From Virtual Testing to HIL Testing - Towards Seamless Testing." In SAE 2014 Aerospace Systems and Technology Conference. 400 Commonwealth Drive, Warrendale, PA, United States: SAE International, 2014. http://dx.doi.org/10.4271/2014-01-2165.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
3

Himmler, Andreas, Jace Allen, and Vivek Moudgal. "Flexible Avionics Testing - From Virtual ECU Testing to HIL Testing." In SAE 2013 AeroTech Congress & Exhibition. 400 Commonwealth Drive, Warrendale, PA, United States: SAE International, 2013. http://dx.doi.org/10.4271/2013-01-2242.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
4

Harrold, Mary Jean. "Testing." In the conference. New York, New York, USA: ACM Press, 2000. http://dx.doi.org/10.1145/336512.336532.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
5

"Testing." In 2008 IEEE International Conference on Automation, Quality and Testing, Robotics. IEEE, 2008. http://dx.doi.org/10.1109/aqtr.2008.4588708.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
6

Hegde, Vaishali. "Compliance testing is NOT reliability testing." In 2010 Annual Reliability and Maintainability Symposium (RAMS). IEEE, 2010. http://dx.doi.org/10.1109/rams.2010.5447981.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
7

Bodoff, David, and Pu Li. "Testing algorithms is like testing students." In the 28th annual international ACM SIGIR conference. New York, New York, USA: ACM Press, 2005. http://dx.doi.org/10.1145/1076034.1076142.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
8

Galhotra, Sainyam, Yuriy Brun, and Alexandra Meliou. "Fairness testing: testing software for discrimination." In ESEC/FSE'17: Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering. New York, NY, USA: ACM, 2017. http://dx.doi.org/10.1145/3106237.3106277.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
9

Petrovic, Goran, Marko Ivankovic, Gordon Fraser, and Rene Just. "Does Mutation Testing Improve Testing Practices?" In 2021 IEEE/ACM 43rd International Conference on Software Engineering (ICSE). IEEE, 2021. http://dx.doi.org/10.1109/icse43902.2021.00087.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
10

Ipate, Florentin, and Raluca Lefticaru. "State-based Testing is Functional Testing." In Testing: Academic and Industrial Conference Practice and Research Techniques - MUTATION (TAICPART-MUTATION 2007). IEEE, 2007. http://dx.doi.org/10.1109/taic.part.2007.26.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen

Berichte der Organisationen zum Thema "Testing"

1

Bergbauer, Annika, Erik Hanushek, and Ludger Woessmann. Testing. Research on Improving Systems of Education (RISE), October 2020. http://dx.doi.org/10.35489/bsg-rise-wp_2018/025.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
2

Bergbauer, Annika, Eric Hanushek, and Ludger Woessmann. Testing. Cambridge, MA: National Bureau of Economic Research, July 2018. http://dx.doi.org/10.3386/w24836.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
3

Beyer, Heidi. Testing WP. Federal Reserve Bank of St. Louis, 2020. http://dx.doi.org/10.20955/wp.2020.049.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
4

patel, vaishali. testing report. Crossref, September 2012. http://dx.doi.org/10.5555/reportdoi.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
5

U.S. Department of Agriculture. testing report. Crossref, 2012. http://dx.doi.org/10.5555/reportdoi2.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
6

Hiller, Gudrun. Testing Factorization. Office of Scientific and Technical Information (OSTI), November 2001. http://dx.doi.org/10.2172/798908.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
7

Wallace, Dolores R., Arthur H. Watson, and Thomas J. McCabe. Structured testing :. Gaithersburg, MD: National Institute of Standards and Technology, 1996. http://dx.doi.org/10.6028/nist.sp.500-235.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
8

Young, Michal. Perpetual Testing. Fort Belvoir, VA: Defense Technical Information Center, February 2003. http://dx.doi.org/10.21236/ada412542.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
9

Osterwell, Leon J., and Lori A. Clarke. Perpetual Testing. Fort Belvoir, VA: Defense Technical Information Center, August 2003. http://dx.doi.org/10.21236/ada418822.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
10

Landis, Christopher B. IPv6 Testing. Fort Belvoir, VA: Defense Technical Information Center, May 2006. http://dx.doi.org/10.21236/ada460472.

Der volle Inhalt der Quelle
APA, Harvard, Vancouver, ISO und andere Zitierweisen
Die Auswahlen zum Thema "Testing" für konkrete Quellenarten können Sie auch interessieren:
Zeitschriftenartikel Dissertationen Bücher
Wir bieten Rabatte auf alle Premium-Pläne für Autoren, deren Werke in thematische Literatursammlungen aufgenommen wurden. Kontaktieren Sie uns, um einen einzigartigen Promo-Code zu erhalten!

Zur Bibliographie