Academic literature on the topic 'Test development'

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 'Test development.'

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 "Test development"

1

Moe, Myint Myint. "Comparative Study of Test-Driven Development TDD, Behavior-Driven Development BDD and Acceptance Test–Driven Development ATDD." International Journal of Trend in Scientific Research and Development Volume-3, Issue-4 (June 30, 2019): 231–34. http://dx.doi.org/10.31142/ijtsrd23698.

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

Moe, Myint Myint. "Unit Test using Test-Driven Development Approach to Support Reusability." International Journal of Trend in Scientific Research and Development Volume-3, Issue-3 (April 30, 2019): 194–96. http://dx.doi.org/10.31142/ijtsrd21731.

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

Dr. Devika R, Dr Devika R. "Development and Standardisation of Inquiry Skills Test." International Journal of Scientific Research 2, no. 9 (June 1, 2012): 137–39. http://dx.doi.org/10.15373/22778179/sep2013/50.

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

Özçelik, Onur, and D. Turgay Altilar. "Test-Driven Approach for Safety-Critical Software Development." Journal of Software 10, no. 7 (July 2015): 904–11. http://dx.doi.org/10.17706//jsw.10.7.904-911.

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

KOGANEI, Reiko, Nobuyuki WATANABE, Kimiaki SASAKI, Yasutaka MAKI, Teruya YAMAGUCHI, and Takayuki SHIMOMURA. "1D15 Development of virtual running test environment to reproduce actual running test(Vehicles-Dynamics)." Proceedings of International Symposium on Seed-up and Service Technology for Railway and Maglev Systems : STECH 2015 (2015): _1D15–1_—_1D15–9_. http://dx.doi.org/10.1299/jsmestech.2015._1d15-1_.

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

Stratigopoulos, H.-G. "Test Metrics Model for Analog Test Development." IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems 31, no. 7 (July 2012): 1116–28. http://dx.doi.org/10.1109/tcad.2012.2185931.

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

UMENO, Takatoshi, Takeshi SHIMOTO, Hidehiko HIGAKI, and Hideaki IWAMOTO. "Development of Agility Test." Proceedings of Mechanical Engineering Congress, Japan 2016 (2016): J2310102. http://dx.doi.org/10.1299/jsmemecj.2016.j2310102.

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

Rupp, André A., and Katrin Böhme. "Handbook of Test Development." International Journal of Testing 8, no. 1 (February 19, 2008): 111–25. http://dx.doi.org/10.1080/15305050701813433.

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

Alzubaidi, Radhi M. "Development of Pressuremeter Test." Advanced Materials Research 718-720 (July 2013): 1129–35. http://dx.doi.org/10.4028/www.scientific.net/amr.718-720.1129.

Full text
Abstract:
Insitu tests are mostly considered to be cheap, quick and they are used sometimes to measure certain insitu properties ,such as modulus and lateral stress not readily evaluated by laboratory tests. A form of insitu investigation which is receiving increasing recognition is the pressuremeter. The pressuremeter devices and tests experienced extensive development in both , the technical aspects and the interpretation theories which been used extensively in several testing laboratories . In the present research a comparison between different theories used to evaluate the pressuremeter tests where different were found when using different results for the same test .
APA, Harvard, Vancouver, ISO, and other styles
10

Kumar, Vikram Sheel, and Molly Webster. "A Test in Development." Clinical Chemistry 59, no. 11 (November 1, 2013): 1680–82. http://dx.doi.org/10.1373/clinchem.2012.199976.

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

Dissertations / Theses on the topic "Test development"

1

Čaušević, Adnan. "Quality of Test Design in Test Driven Development." Doctoral thesis, Mälardalens högskola, Inbyggda system, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-18773.

Full text
Abstract:
One of the most emphasised software testing activities in an Agile environment is the usage of the Test Driven Development (TDD) approach. TDD is a development activity where test cases are created by developers before writing the code, and all for the purpose of guiding the actual development process. In other words, test cases created when following TDD could be considered as a by-product of software development. However, TDD is not fully adopted by the industry, as indicated by respondents from our industrial survey who pointed out that TDD is the most preferred but least practised activity. Our further research identified seven potentially limiting factors for industrial adoption of TDD, out of which one of the prominent factor was lack of developers’ testing skills. We subsequently defined and categorised appropriate quality attributes which describe the quality of test case design when following TDD. Through a number of empirical studies, we have clearly established the effect of “positive test bias”, where the participants focused mainly on the functionality while generating test cases. In other words, there existed less number of “negative test cases” exercising the system beyond the specified functionality, which is an important requirement for high reliability systems. On an average, in our studies, around 70% of test cases created by the participants were positive while only 30% were negative. However, when measuring defect detecting ability of those sets of test cases, an opposite ratio was observed. Defect detecting ability of negative test cases were above 70% while positive test cases contributed only by 30%. We propose a TDDHQ concept as an approach for achieving higher quality testing in TDD by using combinations of quality improvement aspects and test design techniques to facilitate consideration of unspecified requirements during the development to a higher extent and thus minimise the impact of potentially inherent positive test bias in TDD. This way developers do not necessarily focus only on verifying functionality, but they can as well increase security, robustness, performance and many other quality improvement aspects for the given software product. An additional empirical study, evaluating this method, showed a noticeable improvement in the quality of test cases created by developers utilising TDDHQ concept. Our research findings are expected to pave way for further enhancements to the way of performing TDD, eventually resulting in better adoption of it by the industry.
APA, Harvard, Vancouver, ISO, and other styles
2

Knapp, Chris H. "Unlocking test-driven development." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/CKnapp2006.pdf.

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

Algan, Fatih Tuğlular Tuğkan. "Test driven software development/." [s.l.]: [s.n.], 2005. http://library.iyte.edu.tr/tezler/master/bilgisayaryazilimi/T000412.pdf.

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

Kim, Sang-Gil. "DEVELOPMENT OF ECOTOXICOLOGICAL TEST USING CLOSTERIUM EHRENBERGII (AGZI-TEST)." Kyoto University, 1999. http://hdl.handle.net/2433/181803.

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

Bujila, Razvan, and Johan Kuru. "OMSI Test Suite verifier development." Thesis, Linköpings universitet, Institutionen för teknik och naturvetenskap, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-96266.

Full text
Abstract:
The purpose of the Open Mobile Service Interface (OMSI) is to simplify the device management process for mobile devices from different manufacturers with a single PC application, instead of using one unique application for every manufacturer. The different OMSI use cases include device management for application vendors, points-of-sale, repair centers or for self-service. This will lead to higher service level for end users, faster repair times, better control over service transactions, an open market for compatible applications and an easy plug-and-play installation. Manufacturers are currently in the process of developing their own specific modules and there is an increasing need for test and verification software to certify OMSI conformance. In order for phone manufacturers to be able to efficiently verify that their OMSI modules and catalogs support and comply with the OMSI standard, there is a need for automated module tests and manual catalog tests. Development of such tests is the main purpose of this Master thesis work. The implementation of the different verification processes have been divided into different sub-projects to create a more structured view of the OMSI Test Suite project and easier management. The first part of the thesis work deals with the module verification process, second part with the client verification process while the third and final part deals with the catalog verification process. The thesis work has been performed in a project form, where the development of the project plan was a part of the thesis work. The final version of the Module Interface Verifier was implemented in C#, in a Visual Studio .NET 2003 environment. The software functioned as expected, both towards a sample module and Sony Ericsson’s and Nokia’s respective modules. The Client Interface Verifier was developed in a C++ environment and functioned according to the given specifications. The Catalog Interface Verifier was developed in C# environment, built on an already existing part of the OMSI Implementation Framework.
APA, Harvard, Vancouver, ISO, and other styles
6

Shappee, Bartlett A. "Test First Model-Driven Development." Digital WPI, 2012. https://digitalcommons.wpi.edu/etd-theses/339.

Full text
Abstract:
Test Driven Development (TDD), Model-Driven Development (MDD), and Test Case Generation with their associated practices and tools each in their own right promise to deliver robust higher quality code more economically then other approaches. These process are not mutually exclusive but are not typically used together. This thesis develops a combined approach using complimentary aspects of each of the above three process. Test cases are described, generated, and then injected back into the model, which is then used to produce the test and production code. We have enhanced a model-driven tool to support the approach, adding a test case generator, capable of understanding augmented MDD software model and utilizing the constraints captured in our test-centric language to generate model-level test cases back into the model. Our results show that, with a reduction in overall effort one can produce a tested model-based system in which its test and implementation for multiple platforms such as C and Java, using one of multiple test xUnit frameworks.
APA, Harvard, Vancouver, ISO, and other styles
7

Rosén, Annie. "Development of pharmacogenetic tests and improvement of autosomal ancestry DNA test." Thesis, Linköpings universitet, Institutionen för klinisk och experimentell medicin, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-57977.

Full text
Abstract:
This master thesis was performed at the personal genomics company DNA-Guide Europa AB. The goal was to create DNA tests for drug response and to update the already existing DNA test for autosomal ancestry. The DNA tests for drug response: The objective of this part of the master thesis was to create individual DNA test for response to each drug within different groups of medicines. The tests were meant to interest private customers. DNA-Guide uses a microarray technique for the DNA-analysis and this delimited the choice of SNPs. Inserts, deletions, repeats and copies of a whole gene can be difficult to implement on the microarray chip. The SNPs and studies used as a base for the tests had to fulfil several criteria. The studies must be large enough to prove that the association between the genotype and the response to the drug is valid among Europeans, since it’s the clientele of the company. The found association must also be strong enough to be of interest for a DNA test at DNA-Guide. If the SNPs could be implemented on the microarray chip a customer report was created about the possible results. The report had the same structure and design as those for the existing DNA tests at DNA-Guide. The work resulted in DNA tests and reports for medicines within the seven groups of medicines; anticoagulants, medicine against high cholesterol, blood pressure lowering medicine, asthma inhalers, antidepressants, birth-control pills and antiretroviral drugs. The DNA test for autosomal ancestry: The purpose of the update was to enhance to customers understanding of their results and the construction of the test. The update resulted in a description of how the used algorithm processes the results (from the DNA analysis) and a guide to interpret the results of the test. Conclusions: Both the DNA tests for drug response and the updated DNA test for autosomal ancestry can add value for the customers at DNA-Guide. The DNA tests for drug response can offer an explanation to why a medicine does not have an effect or reveal if the customer has higher risk of adverse effects. Even though recommendations for dosage or treatment could not be provided in almost all of the created DNA tests, being aware of the higher risk can be the first step to avoid adverse effects. The update of the DNA test report for autosomal ancestry resulted in a better description of the algorithm and limitations of the test, which can enhance the customers’ understanding of their results.
APA, Harvard, Vancouver, ISO, and other styles
8

Halliday, Tracey Jaye. "The Development of a New Zealand Adult Reading Test." The University of Waikato, 2006. http://hdl.handle.net/10289/2494.

Full text
Abstract:
The National Adult Reading Test (NART), developed in Britain is commonly used in clinical settings to estimate premorbid intelligence in New Zealand. Research suggests psychometric tests are more accurate if normed on the population they are used with. This study attempted to establish norms for the original NART based on a New Zealand population and develop a National Adult Reading Test for use with a New Zealand population (NZART). Sixty-four university students were administered the Wechslers Abbreviated Scale of Intelligence (WASI), the NART and the New Zealand Adult Reading Test (NZART). A regression equation was developed to estimate premorbid intelligence in this sample. Results indicate fewer errors occur on the NZART than the NART suggesting it may be a better indicator of premorbid intelligence for a New Zealand sample. Furthermore, the NZART was more accurate at estimating premorbid WASI IQ across all three subscales of the WASI at a range of IQ levels. Analyses were also conducted to ascertain the impact of demographic variables. Little overall difference was found in test scores in relation to gender, age or income. Although future studies need to be conducted to validate this new measure, initial results suggest that the NZART may be a more accurate predictor of premorbid IQ in a New Zealand population.
APA, Harvard, Vancouver, ISO, and other styles
9

Khan, Hassan Mahmood, and Ibrar Arshad. "Test-lists Utilization in Test Driven Development : The Role of test-lists in Requirements Traceability." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4782.

Full text
Abstract:
Context: In recent times, many organizations have started using agile software development methodologies instead of using traditional methodologies. The main reason for this shift is the ability of agile approaches to cope with changes in the requirements, customer satisfaction and assurance of on-time delivery of quality products [19]. Test-Driven Development (TDD) is a software development methodology that is considered to be one of the most prominent practices of eXtreme Programming (XP) (an agile methodology) [1][9][10]. Test-list in TDD is considered as a temporary repository in which test items are stored and later by using those items test cases are developed. Requirements Traceability is also a major problem in agile development mainly because of lack of formal requirements specification and frequent requirements change. Objectives: This study explores the utilization of test-list and possibility of using test-list for requirements traceability in TDD. This study describes concept of test-list, its formation and exploring its utilization in TDD. Methods for implementing requirements traceability in and identification of possibility of utilizing test-list for requirements traceability in TDD is also explored. Methods: Methods used in this study are systematic literature review, surveys and interviews. Systematic literature review was done using seven electronic databases, including Inspec, IEEE Xplore, ACM Digital Library, Springer, Science Direct and Scopus. Studies were selected on the bases of preliminary, basic and advanced developed criteria. Survey was conducted using online questionnaire from TDD practitioners. Findings from literature review and surveys were used to develop interview questionnaires. Interviews were conducted from the same practitioners that were involved in surveys. Results: Based on the findings of literature review, questionnaire and interviews, we obtained TDD practices for test-list development and requirements traceability. Analysis was performed on results of SLR and questionnaire and possibility of using test-list for requirements traceability was identified. Based on the analysis of literature review and surveys, interview questionnaire were developed to further investigate the area of interest. We have found that in literature there is no defined method to develop test-list. and survey participants also confirms it. Majority of survey participants create test-list temporarily and informal. On question of whether test-list can be use for requirements traceability around 70% of participants are agree for its use. Interview respondents also confirm the findings of survey. Conclusions: Literature has not provided any test-list development method and practitioners also have no clear guideline to develop test-list prior to Test development. Systematic literature review and practitioner’s survey and interviews confirm it. Literature is also silent for any specific requirements change management or requirements traceability method in TDD. We identified requirements traceability practices in agile and management through literature and survey. After analysis of gathered data we found TDD lacks in test-list formalization, none of the study focuses on requirements traceability in TDD. In this study our contribution is exploration of test-list creation and utilization through literature and state of the practice; after practitioners feedback we also explored that test-list can be used for requirements traceability.
hasmkh@gmail.com, ibrararshad@gmail.com
APA, Harvard, Vancouver, ISO, and other styles
10

Ispir, Mustafa. "Test Driven Development Of Embedded Systems." Master's thesis, METU, 2004. http://etd.lib.metu.edu.tr/upload/12605630/index.pdf.

Full text
Abstract:
In this thesis, the Test Driven Development method (TDD) is studied for use in developing embedded software. The required framework is written for the development environment Rhapsody. Integration of TDD into a classical development cycle, without necessitating a transition to agile methodologies of software development and required unit test framework to apply TDD to an object oriented embedded software development project with a specific development environment and specific project conditions are done in this thesis. A software tool for unit testing is developed specifically for this purpose, both to support the proposed approach and to illustrate its application. The results show that RhapUnit supplies the required testing functionality for developing embedded software in Rhapsody with TDD. Also, development of RhapUnit is a successful example of the application of TDD.
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Test development"

1

Madeyski, Lech. Test-Driven Development. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-04288-1.

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

Test-driven iOS development. Upper Saddle River, NJ: Addison-Wesley, 2012.

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

M, Downing Steven, and Haladyna Thomas M, eds. Handbook of test development. Mahwah, N.J: Erlbaum, 2006.

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

Test-driven JavaScript development. Upper Saddle River, NJ: Addison-Wesley, 2011.

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

Test-driven development: By example. Boston: Addison-Wesley, 2003.

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

Qiu, Juntao. Test-Driven Development with React. Berkeley, CA: Apress, 2021. http://dx.doi.org/10.1007/978-1-4842-6972-5.

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

Lodi, Gio. Test-Driven Development in Swift. Berkeley, CA: Apress, 2021. http://dx.doi.org/10.1007/978-1-4842-7002-8.

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

Paranj, Bala. Test Driven Development in Ruby. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2638-4.

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

T, Miller Cass, Yoon Jeyong, and U.S. Army Engineer Waterways Experiment Station, eds. Dredging Elutriate Test (DRET) development. Vicksburg, Miss: US Army Corps of Engineers, Waterways Experiment Station, 1995.

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

Raymond, Mark R. Guide to test item development. Kansas City, Mo. (2420 Pershing Rd., Kansas City 64108): American Nurses' Association, 1986.

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

Book chapters on the topic "Test development"

1

Rosenfield Boeira, Julia Naomi. "Test, Code, Test." In Lean Game Development, 89–99. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3216-3_9.

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

Irwing, Paul, and David J. Hughes. "Test Development." In The Wiley Handbook of Psychometric Testing, 1–47. Chichester, UK: John Wiley & Sons, Ltd, 2018. http://dx.doi.org/10.1002/9781118489772.ch1.

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

Mendelovits, Juliette. "Test Development." In Implementation of Large-Scale Education Assessments, 63–91. Chichester, UK: John Wiley & Sons, Ltd, 2017. http://dx.doi.org/10.1002/9781118762462.ch3.

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

Lalanne, Christian. "Test Factor." In Specification Development, 301–20. Chichester, UK: John Wiley & Sons, Ltd, 2014. http://dx.doi.org/10.1002/9781118931219.ch10.

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

Dāsa, Rādhārādhya. "Test-Driven Development." In Learn CakePHP, 18–21. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-1212-7_4.

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

Anandakrishnan, Sridhar. "Test-Driven Development." In Propeller Programming, 45–52. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-3354-2_4.

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

Nolan, Godfrey. "Test Driven Development." In Agile Swift, 131–67. Berkeley, CA: Apress, 2016. http://dx.doi.org/10.1007/978-1-4842-2102-0_6.

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

Roth, Stephan. "Test-Driven Development." In Clean C++, 191–215. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-2793-0_8.

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

Rosenfield Boeira, Julia Naomi. "Test-Driven Development." In Lean Game Development, 53–66. Berkeley, CA: Apress, 2017. http://dx.doi.org/10.1007/978-1-4842-3216-3_6.

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

Dalton, Jeff. "Test-Driven Development." In Great Big Agile, 263–64. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-4206-3_67.

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

Conference papers on the topic "Test development"

1

Leitner, Andreas, Ilinca Ciupa, Oriol Manuel, Bertrand Meyer, and Arno Fiva. "Contract driven development = test driven development - writing test cases." In the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium. New York, New York, USA: ACM Press, 2007. http://dx.doi.org/10.1145/1287624.1287685.

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

Lopes Lagos, Rafael, Luiz Fernando Braga Lopes, and Jasmin Moreira. "BARTLE’S TEST – REINVENTING THE TEST." In 13th International Technology, Education and Development Conference. IATED, 2019. http://dx.doi.org/10.21125/inted.2019.0672.

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

Hammond, Susan, and David Umphress. "Test driven development." In the 50th Annual Southeast Regional Conference. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2184512.2184550.

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

Bijlsma, A., H. J. M. Passier, H. J. Pootjes, and S. Stuurman. "Integrated Test Development." In the 7th Computer Science Education Research Conference. New York, New York, USA: ACM Press, 2018. http://dx.doi.org/10.1145/3289406.3289408.

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

Isker III, Bernard J., G. Sheffield, John Gonzales, Rebecca A. Batterson, and Glenn M. Kuse. "Cryoprober test development." In Aerospace Sensing, edited by Raymond S. Balcerak, Paul W. Pellegrini, and Dean A. Scribner. SPIE, 1992. http://dx.doi.org/10.1117/12.137775.

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

McDaid, Kevin, Alan Rust, and Brian Bishop. "Test-driven development." In the 4th international workshop. New York, New York, USA: ACM Press, 2008. http://dx.doi.org/10.1145/1370847.1370853.

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

Rodríguez-Pérez, Angel Mariano, Julio José Caparrós-Mancera, and José Antonio Hernandez-Torres. "TRACTION TEST FOR CAST MANUFACTURING TEST PIECES." In 16th International Technology, Education and Development Conference. IATED, 2022. http://dx.doi.org/10.21125/inted.2022.0926.

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

Chen, Mingjing, and Alex Orailoglu. "Test cost minimization through adaptive test development." In 2008 IEEE International Conference on Computer Design (ICCD). IEEE, 2008. http://dx.doi.org/10.1109/iccd.2008.4751867.

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

Shelton, William, Nan Li, Paul Ammann, and Jeff Offutt. "Adding Criteria-Based Tests to Test Driven Development." In 2012 IEEE Fifth International Conference on Software Testing, Verification and Validation (ICST). IEEE, 2012. http://dx.doi.org/10.1109/icst.2012.191.

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

Kamran, Arezoo, Nastaran Nemati, Somayeh Sadeghi Kohan, and Zainalabedin Navabi. "Virtual tester development using HDL/PLI." In Test Symposium (EWDTS). IEEE, 2010. http://dx.doi.org/10.1109/ewdts.2010.5742156.

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

Reports on the topic "Test development"

1

Woloshun, Keith Albert. Disk Mechanical Test Development. Office of Scientific and Technical Information (OSTI), June 2015. http://dx.doi.org/10.2172/1188151.

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

Ashok Kush. MCFC PRODUCT DEVELOPMENT TEST. Office of Scientific and Technical Information (OSTI), August 1998. http://dx.doi.org/10.2172/835051.

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

Ebbinghaus, B. B. Form development sample test matrix. Office of Scientific and Technical Information (OSTI), October 1999. http://dx.doi.org/10.2172/15013105.

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

Fuhrmann, M., R. F. Pietrzak, J. Heiser, E. M. Franz, and P. Colombo. Accelerated leach test development program. Office of Scientific and Technical Information (OSTI), November 1990. http://dx.doi.org/10.2172/6218696.

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

Reeves, John, and Larry McKee. A Test Planning Methodology From Concept Development Through Test Execution. Fort Belvoir, VA: Defense Technical Information Center, November 1999. http://dx.doi.org/10.21236/ada385298.

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

Paul A. Demkowicz. Lead Coolant Test Facility Development Workshop. Office of Scientific and Technical Information (OSTI), June 2005. http://dx.doi.org/10.2172/911227.

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

HUBER, J. H. ENRAF annulus leak detector development test. Office of Scientific and Technical Information (OSTI), May 1999. http://dx.doi.org/10.2172/782315.

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

Morrissey, Ryan J., Garth Wilks, Michael Uchic, and Reji John. Thin Foil Test System Development (Preprint). Fort Belvoir, VA: Defense Technical Information Center, February 2009. http://dx.doi.org/10.21236/ada512759.

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

Harkins, Thomas K. Development, Theory & Some Test Results. Fort Belvoir, VA: Defense Technical Information Center, April 2001. http://dx.doi.org/10.21236/ada386278.

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

Weissmuller, Johnny J., Martin J. Dittmar, and William J. Phalen. Automated Test Outline Development: Research Findings. Fort Belvoir, VA: Defense Technical Information Center, November 1989. http://dx.doi.org/10.21236/ada215401.

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