Search for dissertations about: "developer testing"
Showing result 1 - 5 of 11 swedish dissertations containing the words developer testing.
-
1. Language-Based Techniques and Stochastic Models for Automated Testing
Abstract : As software systems become bigger and scarier, automating their testing is crucial to ensure that our confidence in them can keep up with their growth. In this setting, Generational Fuzzing and Random Property-Based Testing are two sides of the same testing technique that can help us find bugs effectively without having to spend countless hours writing unit tests by hand. READ MORE
-
2. Quality of Test Design in Test Driven Development
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. READ MORE
-
3. Biomimetic Software Engineering Techniques for Dependability
Abstract : The powerful information processing capabilities of computers have made them an indispensable part of our modern societies. As we become more reliant on computers and want them to handle more critical and difficult tasks it becomes important that we can depend on the software that controls them. READ MORE
-
4. Automating Black-Box Property Based Testing
Abstract : Black-box property based testing tools like QuickCheck allow developers to write elegant logical specifications of their programs, while still permitting unrestricted use of the same language features and libraries that simplify writing the programs themselves. This is an improvement over unit testing because a single property can replace a large collection of testcases, and over more heavy-weight white-box testing frameworks that impose restrictions on how properties and tested code are written. READ MORE
-
5. The Hole Story: Type-Directed Synthesis and Repair
Abstract : Modern programs in languages like Haskell include a lot of information beyond what is strictly required for compilation, such as additional type information, unit tests and properties. This information is often used for post-compilation verification, by running the tests to verify that the code-as-written matches the specification provided by the types and properties. READ MORE