Patterns in Testing
•
0 likes•655 views
The document discusses different types of software testing including unit testing, functional testing, and user driven testing. It explains why writing tests is important to catch defects, document code, and allow for safer changes. The document also discusses balancing purism with pragmatism in testing and different strategies for testing new code versus legacy code, including test-driven development and characterizing existing behaviors. It provides examples of testing frameworks for different languages and emphasizes integrating testing into the development and build process through continuous integration.
Report
Share
Report
Share
Recommended
Unit testing
This document discusses unit testing and provides an overview of its benefits and best practices. It defines unit testing as testing small pieces of code in isolation. It recommends writing unit tests for all code to check functionality and prevent bugs, and integrating testing into the development process by writing tests before code and ensuring tests pass before check-ins. The document also discusses test-driven development, refactoring code based on test results, and tools like NUnit that can automate the testing process.
Unit testing
The document outlines five phases of software testing: development, system and integration, user acceptance, implementation, and regression testing. It describes unit testing as focusing on testing individual code units for functionality and reliability. Unit tests are conducted during the development phase using structural or functional techniques. Entry criteria for unit testing include having 80% complete and approved business requirements, a finalized technical design, and an established development environment. Exit criteria include holding a testing transition meeting where developers sign off and receiving project manager approval.
Software testing tools (free and open source)
This document discusses various tools used for test automation including Cobertura, Selenium, JMeter, Bugzilla, and Testia Tarantula. Cobertura is a code coverage tool that calculates test coverage percentages. Selenium is described as a tool for automating web application testing across browsers. JMeter is introduced as a load testing tool focused on analyzing performance of web applications. Bugzilla and Tarantula are mentioned as tools for bug tracking and project/test management respectively in agile software development. The document also discusses integrating these various tools together for a complete test automation framework.
Software Testing without Requirements: Survival Guide
This document discusses software testing techniques that can be used in situations where there is little time or documentation available. It recommends an approach of exploratory testing, learning about the product through exploration and interviews, and creating documentation throughout the testing process in a top-down and bottom-up manner. Specific techniques mentioned include risk-based testing, logging test scenarios, confirming results, learning about users, objects, workflows and properties of the product, visualizing system requirements, starting with high-level documentation and adding details while testing. The approach is to repeat exploratory testing and documentation to continually learn more about the product.
Unit Testing
Unit Testing presentation going through advantages, naming convention, testing frameworks, mocking frameworks...
Qa mockup interview for automation testing
This document provides an agenda and guidelines for an interview for an automation testing role. It includes preparation tips for candidates such as researching the company, practicing common interview questions, and preparing their own questions. It also lists sample interview questions related to automation testing processes, tools, frameworks, and challenges. The questions cover topics like the automation testing process, test selection, automation tools, method overloading, interfaces, locators, working with windows, exposure to frameworks, and common project questions. References for additional practice interview questions are also included.
Testing concepts ppt
Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.
Tech talks annual 2015 izzet mustafayev_performance testing - the way to make...
This document discusses performance testing for web applications. It introduces why performance testing is important, what it is, and how to conduct it. Performance testing determines how a system performs under different workloads by measuring aspects like availability, response time, and throughput. The document recommends testing at various load levels, monitoring applications during tests, using the right tools to minimize impact, and automating testing processes. It promotes continuous performance testing with sufficient data and time.
Recommended
Unit testing
This document discusses unit testing and provides an overview of its benefits and best practices. It defines unit testing as testing small pieces of code in isolation. It recommends writing unit tests for all code to check functionality and prevent bugs, and integrating testing into the development process by writing tests before code and ensuring tests pass before check-ins. The document also discusses test-driven development, refactoring code based on test results, and tools like NUnit that can automate the testing process.
Unit testing
The document outlines five phases of software testing: development, system and integration, user acceptance, implementation, and regression testing. It describes unit testing as focusing on testing individual code units for functionality and reliability. Unit tests are conducted during the development phase using structural or functional techniques. Entry criteria for unit testing include having 80% complete and approved business requirements, a finalized technical design, and an established development environment. Exit criteria include holding a testing transition meeting where developers sign off and receiving project manager approval.
Software testing tools (free and open source)
This document discusses various tools used for test automation including Cobertura, Selenium, JMeter, Bugzilla, and Testia Tarantula. Cobertura is a code coverage tool that calculates test coverage percentages. Selenium is described as a tool for automating web application testing across browsers. JMeter is introduced as a load testing tool focused on analyzing performance of web applications. Bugzilla and Tarantula are mentioned as tools for bug tracking and project/test management respectively in agile software development. The document also discusses integrating these various tools together for a complete test automation framework.
Software Testing without Requirements: Survival Guide
This document discusses software testing techniques that can be used in situations where there is little time or documentation available. It recommends an approach of exploratory testing, learning about the product through exploration and interviews, and creating documentation throughout the testing process in a top-down and bottom-up manner. Specific techniques mentioned include risk-based testing, logging test scenarios, confirming results, learning about users, objects, workflows and properties of the product, visualizing system requirements, starting with high-level documentation and adding details while testing. The approach is to repeat exploratory testing and documentation to continually learn more about the product.
Unit Testing
Unit Testing presentation going through advantages, naming convention, testing frameworks, mocking frameworks...
Qa mockup interview for automation testing
This document provides an agenda and guidelines for an interview for an automation testing role. It includes preparation tips for candidates such as researching the company, practicing common interview questions, and preparing their own questions. It also lists sample interview questions related to automation testing processes, tools, frameworks, and challenges. The questions cover topics like the automation testing process, test selection, automation tools, method overloading, interfaces, locators, working with windows, exposure to frameworks, and common project questions. References for additional practice interview questions are also included.
Testing concepts ppt
Testing involves finding errors in a program. The goal is to assume a program contains errors and test to find as many as possible. Different testing techniques include white box testing by developers and black box testing by testers. Testing levels include unit, integration, system, and user acceptance testing. Developers and testers have different goals - developers want code to work while testers try to make code fail. Good development practices from a tester's view include doing own acceptance tests, fixing bugs, writing helpful error messages, and not artificially adding bugs. Good relationships between project managers, developers and testers help ensure quality.
Tech talks annual 2015 izzet mustafayev_performance testing - the way to make...
This document discusses performance testing for web applications. It introduces why performance testing is important, what it is, and how to conduct it. Performance testing determines how a system performs under different workloads by measuring aspects like availability, response time, and throughput. The document recommends testing at various load levels, monitoring applications during tests, using the right tools to minimize impact, and automating testing processes. It promotes continuous performance testing with sufficient data and time.
Unit Testing
The document discusses unit testing and provides guidance on how to effectively implement unit testing. It defines unit testing as testing individual units or components of software code to verify they are functioning as intended. The document outlines best practices for unit testing such as writing test cases that cover valid, invalid, and boundary conditions. It also recommends testing frameworks like JUnit that can automate running test cases. Overall, the document advocates for developing a rigorous unit testing strategy and practicing habits like writing tests first and continuously running tests to improve code quality.
Automation frameworks
Slide covers about why to automation, what are frameworks available and understanding each framework. Comparison/advantages of each framework.
Testing Tools
Not long ago, testing Ajax components meant play-testing a page by hand. Today, there are a growing number of tools we can use to simplify and automate Ajax testing.
In this session we will cover when to test, what to test and how to test Ajax components. You learn how to create automatic tests with various tools, including YUI Test, and OpenQA Selenium, and how to use Ajax testing tools with IDEs and Continuous Integration systems.
In this session, you will learn:
* When, where and how to test Ajax components;
* How to create automatic tests with various tools;
* How to use Ajax testing tools with IDEs and Continuous Integration systems.
ISTQB Foundation Level Certification - Intruduction
What is ISTQB? What does Foundation Level mean? Why do I need a certificate and how can I get it? You'll know from this presentation.
Top 15 Interview Questions for Manual Testers
Preparing for an interview as a manual tester? Here is a bit of help. For some technical edge, it is obviously useful to have an idea about what most interviewers ask. I have prepared a short list of the most commonly asked manual testing interview questions, along with their answers. Let’s jump right in!
Automated Testing vs Manual Testing
Manual testing takes more effort and cost than automated testing. It is more boring and provides limited visibility for stakeholders. Automated tests can test single units, are reusable, and provide a safety net for refactoring. They also ensure all tests are run, drive clean design, and do not create code clutter like manual tests. An initial learning curve and questions around organization and reuse may prevent developers from writing automated tests, but designating responsibility and learning tools can help overcome these issues.
Unit testing basics with NUnit and Visual Studio
Unit testing in .NET provides several benefits such as encouraging better design, serving as documentation, and providing a safety net for refactoring. There are different types of tests like unit, integration, user acceptance, and test-driven development tests. A unit test invokes a method or class and checks assumptions about its logical behavior. Unit tests exercise single units of code while integration tests exercise how units work together. Tests should target logical code with decisions. Good tests are automated, easy to implement, run quickly, and can be run by anyone at any time. The document outlines guidelines for creating test projects, classes, and methods along with .NET testing frameworks, techniques like mocking and dependency injection, code coverage, and qualities of trust
ISTQB Eğitim Sunumu
ISTQB eğitiminde yazılım testi ile ilgili önemli konulara ve örneklere değinilmiştir. "Test Nedir?", "Testin Prensipleri", "Test Teknikleri", "Yazılım Metodolojileri" ve daha birçok önemli başlık hakkında detaylı ve teknik bilgiler yaşanmış örneklerle verilmiştir. Bu sunumda, bahsedilen konu başlıkları ve daha fazlası genel haliyle anlatılmıştır.
Formal method
The document discusses two SAT solvers: MINISAT and SPEAR. MINISAT is a minimalistic and open-source SAT solver that is highly efficient. SPEAR is an arithmetic theorem prover and SAT solver designed for software verification; it models features after MINISAT but improves clause minimization. The document analyzes SPEAR and MINISAT, concluding that SPEAR is better suited for parameter optimization due to its configurable parameters and improved clause minimization approach.
Software Testing or Quality Assurance
software testing is necessary to make sure the product or application is defect free, as per customer specifications. Software testing identifies fault whose removal increases the software Quality and Increases the software reliability.Testing effort is directly proportional to the complexity of the program.
Type mock isolator
This document discusses unit testing and mock frameworks. It defines common terms like unit test, fake, stub, and mock. It describes the strengths and weaknesses of unit testing. It then introduces TypeMock as a mock framework that can fake static, sealed, or non-public elements without requiring design changes for testability. The document also briefly debates the pros and cons of dictating design for testability and mentions some research on the benefits of test-driven development.
Manual testing
Manual testing is the process of manually testing software for defects by playing the role of an end user and using all features of the application to ensure correct behavior, following a written test plan. The document discusses various concepts related to manual testing including software quality assurance, verification, validation, software life cycles, testing techniques like black box testing and white box testing, unit testing, alpha testing, beta testing, system testing, volume testing, stress testing, and security testing. It provides brief definitions and purposes of these concepts.
Software testing
The document discusses various types and levels of software testing. It defines software testing as analyzing a software item to detect differences between existing and required conditions (i.e. defects). The key types discussed are positive and negative testing, white-box and black-box testing. The levels covered are unit testing, integration testing, system testing, and acceptance testing. Various testing tools are also listed for different testing purposes such as source code testing, functional testing, performance testing, and database testing.
Automated Testing DITA Content and Customizations
The document discusses various methods for automated testing of DITA content and output, including using Schematron for validating content structure, the QA plugin for identifying tagging errors, XMLUnit for comparing XML, and the DITA OT regression test for validating the output of the open-source DITA Open Toolkit. It also covers automating browser tests using Selenium and comparing HTML output using Needle and Nose. Demo examples are provided for several of these automated testing tools and techniques.
Intro to Manual Testing
Manual testing involves manually testing software by playing the role of an end user and using test cases to ensure correct behavior. It is important early in development when automation is not possible and for testing visual elements. A test plan is a document that outlines test objectives, workflows and processes while a test case specifies conditions to determine if a feature works as intended. Both exploratory and black/white box testing have pros and cons for finding bugs. Bugzilla is a bug tracking system that helps developers manage issues.
Software Testing Interview Questions & Answers | Edureka
Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses **
This Edureka PPT on Top 50 Software Testing Interview Question and Answers will help you to prepare yourself for Software Testing Interviews. It covers questions for beginners, intermediate and experienced professionals.
Below topics are covered in this PPT:
Market Trends in Software Testing
What is Software testing
Top 50 interview questions
1. Beginners level questions
2. Intermediate level questions
3. Advance level questions
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Testing JavaScript Applications
This slide goes from an introduction to general software testing down to testing of javascript application, explaining why test, when to test and what to test in an application. Mocha framework was used to explain how testing works in JS.
Talk Presented at #forLoopKaduna Meetup on July 1st, 2017
Testing concept definition
The document discusses various types of software testing concepts including manual vs automated testing, test beds, test data, positive and negative test cases, defect priority and severity levels, test plans, security and recovery testing, and more. It provides definitions and explanations of these key testing concepts.
Automation testing interview pdf org
This document contains commonly asked automation testing interview questions and their answers to help prepare for an interview. It discusses reasons for automation testing, factors in deciding what to automate, benefits of tools like Quick Test Pro and Selenium, the automation testing process, and challenges like maintaining automated tests. Specific questions cover topics like test frameworks, best practices, and when not to automate. The goal is to help interviewees have answers on their fingertips for a wide range of potential automation testing questions.
Testing a GPS application | Testbytes
The document describes testing procedures for a GPS application. It discusses hurdles in GPS testing like signal fluctuations with barriers and weather. It outlines the test strategy used including functional, load, performance, and field testing. The main testing focuses are on functionality, network connectivity, usability, scalability, security, and performance. GPS module testing procedures are described including using simulators, collecting real trip data, and analyzing signal strength and location data. JMeter is used for load and performance testing, and custom tools are created for issue tracking.
Agile for game_development
This document discusses using agile methodologies like Scrum for game development. It provides an overview of key agile terms like stories, sprints, and retrospectives. It explains that agile aims to smooth out the development process and accommodate change. Scrum is presented as a common agile framework that uses short iterations to deliver working software frequently for feedback. The document also covers how lean principles can be applied to formalize content production phases in game development.
Single Content Streams
A single content stream is a way to generate content once and distribute it across multiple social media services. The content stream score (CSS) measures the breadth of a single content stream by counting the number of transitions between different content formats and platforms. A higher CSS indicates the content reaches a wider audience. Examples are provided of content streams with CSS from 2 to 15 by distributing content from blogs, microblogs, media, livestreams, and aggregates across different social media platforms.
More Related Content
What's hot
Unit Testing
The document discusses unit testing and provides guidance on how to effectively implement unit testing. It defines unit testing as testing individual units or components of software code to verify they are functioning as intended. The document outlines best practices for unit testing such as writing test cases that cover valid, invalid, and boundary conditions. It also recommends testing frameworks like JUnit that can automate running test cases. Overall, the document advocates for developing a rigorous unit testing strategy and practicing habits like writing tests first and continuously running tests to improve code quality.
Automation frameworks
Slide covers about why to automation, what are frameworks available and understanding each framework. Comparison/advantages of each framework.
Testing Tools
Not long ago, testing Ajax components meant play-testing a page by hand. Today, there are a growing number of tools we can use to simplify and automate Ajax testing.
In this session we will cover when to test, what to test and how to test Ajax components. You learn how to create automatic tests with various tools, including YUI Test, and OpenQA Selenium, and how to use Ajax testing tools with IDEs and Continuous Integration systems.
In this session, you will learn:
* When, where and how to test Ajax components;
* How to create automatic tests with various tools;
* How to use Ajax testing tools with IDEs and Continuous Integration systems.
ISTQB Foundation Level Certification - Intruduction
What is ISTQB? What does Foundation Level mean? Why do I need a certificate and how can I get it? You'll know from this presentation.
Top 15 Interview Questions for Manual Testers
Preparing for an interview as a manual tester? Here is a bit of help. For some technical edge, it is obviously useful to have an idea about what most interviewers ask. I have prepared a short list of the most commonly asked manual testing interview questions, along with their answers. Let’s jump right in!
Automated Testing vs Manual Testing
Manual testing takes more effort and cost than automated testing. It is more boring and provides limited visibility for stakeholders. Automated tests can test single units, are reusable, and provide a safety net for refactoring. They also ensure all tests are run, drive clean design, and do not create code clutter like manual tests. An initial learning curve and questions around organization and reuse may prevent developers from writing automated tests, but designating responsibility and learning tools can help overcome these issues.
Unit testing basics with NUnit and Visual Studio
Unit testing in .NET provides several benefits such as encouraging better design, serving as documentation, and providing a safety net for refactoring. There are different types of tests like unit, integration, user acceptance, and test-driven development tests. A unit test invokes a method or class and checks assumptions about its logical behavior. Unit tests exercise single units of code while integration tests exercise how units work together. Tests should target logical code with decisions. Good tests are automated, easy to implement, run quickly, and can be run by anyone at any time. The document outlines guidelines for creating test projects, classes, and methods along with .NET testing frameworks, techniques like mocking and dependency injection, code coverage, and qualities of trust
ISTQB Eğitim Sunumu
ISTQB eğitiminde yazılım testi ile ilgili önemli konulara ve örneklere değinilmiştir. "Test Nedir?", "Testin Prensipleri", "Test Teknikleri", "Yazılım Metodolojileri" ve daha birçok önemli başlık hakkında detaylı ve teknik bilgiler yaşanmış örneklerle verilmiştir. Bu sunumda, bahsedilen konu başlıkları ve daha fazlası genel haliyle anlatılmıştır.
Formal method
The document discusses two SAT solvers: MINISAT and SPEAR. MINISAT is a minimalistic and open-source SAT solver that is highly efficient. SPEAR is an arithmetic theorem prover and SAT solver designed for software verification; it models features after MINISAT but improves clause minimization. The document analyzes SPEAR and MINISAT, concluding that SPEAR is better suited for parameter optimization due to its configurable parameters and improved clause minimization approach.
Software Testing or Quality Assurance
software testing is necessary to make sure the product or application is defect free, as per customer specifications. Software testing identifies fault whose removal increases the software Quality and Increases the software reliability.Testing effort is directly proportional to the complexity of the program.
Type mock isolator
This document discusses unit testing and mock frameworks. It defines common terms like unit test, fake, stub, and mock. It describes the strengths and weaknesses of unit testing. It then introduces TypeMock as a mock framework that can fake static, sealed, or non-public elements without requiring design changes for testability. The document also briefly debates the pros and cons of dictating design for testability and mentions some research on the benefits of test-driven development.
Manual testing
Manual testing is the process of manually testing software for defects by playing the role of an end user and using all features of the application to ensure correct behavior, following a written test plan. The document discusses various concepts related to manual testing including software quality assurance, verification, validation, software life cycles, testing techniques like black box testing and white box testing, unit testing, alpha testing, beta testing, system testing, volume testing, stress testing, and security testing. It provides brief definitions and purposes of these concepts.
Software testing
The document discusses various types and levels of software testing. It defines software testing as analyzing a software item to detect differences between existing and required conditions (i.e. defects). The key types discussed are positive and negative testing, white-box and black-box testing. The levels covered are unit testing, integration testing, system testing, and acceptance testing. Various testing tools are also listed for different testing purposes such as source code testing, functional testing, performance testing, and database testing.
Automated Testing DITA Content and Customizations
The document discusses various methods for automated testing of DITA content and output, including using Schematron for validating content structure, the QA plugin for identifying tagging errors, XMLUnit for comparing XML, and the DITA OT regression test for validating the output of the open-source DITA Open Toolkit. It also covers automating browser tests using Selenium and comparing HTML output using Needle and Nose. Demo examples are provided for several of these automated testing tools and techniques.
Intro to Manual Testing
Manual testing involves manually testing software by playing the role of an end user and using test cases to ensure correct behavior. It is important early in development when automation is not possible and for testing visual elements. A test plan is a document that outlines test objectives, workflows and processes while a test case specifies conditions to determine if a feature works as intended. Both exploratory and black/white box testing have pros and cons for finding bugs. Bugzilla is a bug tracking system that helps developers manage issues.
Software Testing Interview Questions & Answers | Edureka
Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses **
This Edureka PPT on Top 50 Software Testing Interview Question and Answers will help you to prepare yourself for Software Testing Interviews. It covers questions for beginners, intermediate and experienced professionals.
Below topics are covered in this PPT:
Market Trends in Software Testing
What is Software testing
Top 50 interview questions
1. Beginners level questions
2. Intermediate level questions
3. Advance level questions
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
Software Testing Blog playlist: http://bit.ly/2UXwdJm
Follow us to never miss an update in the future.
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Testing JavaScript Applications
This slide goes from an introduction to general software testing down to testing of javascript application, explaining why test, when to test and what to test in an application. Mocha framework was used to explain how testing works in JS.
Talk Presented at #forLoopKaduna Meetup on July 1st, 2017
Testing concept definition
The document discusses various types of software testing concepts including manual vs automated testing, test beds, test data, positive and negative test cases, defect priority and severity levels, test plans, security and recovery testing, and more. It provides definitions and explanations of these key testing concepts.
Automation testing interview pdf org
This document contains commonly asked automation testing interview questions and their answers to help prepare for an interview. It discusses reasons for automation testing, factors in deciding what to automate, benefits of tools like Quick Test Pro and Selenium, the automation testing process, and challenges like maintaining automated tests. Specific questions cover topics like test frameworks, best practices, and when not to automate. The goal is to help interviewees have answers on their fingertips for a wide range of potential automation testing questions.
Testing a GPS application | Testbytes
The document describes testing procedures for a GPS application. It discusses hurdles in GPS testing like signal fluctuations with barriers and weather. It outlines the test strategy used including functional, load, performance, and field testing. The main testing focuses are on functionality, network connectivity, usability, scalability, security, and performance. GPS module testing procedures are described including using simulators, collecting real trip data, and analyzing signal strength and location data. JMeter is used for load and performance testing, and custom tools are created for issue tracking.
What's hot (20)
ISTQB Foundation Level Certification - Intruduction
ISTQB Foundation Level Certification - Intruduction
Software Testing Interview Questions & Answers | Edureka
Software Testing Interview Questions & Answers | Edureka
Viewers also liked
Agile for game_development
This document discusses using agile methodologies like Scrum for game development. It provides an overview of key agile terms like stories, sprints, and retrospectives. It explains that agile aims to smooth out the development process and accommodate change. Scrum is presented as a common agile framework that uses short iterations to deliver working software frequently for feedback. The document also covers how lean principles can be applied to formalize content production phases in game development.
Single Content Streams
A single content stream is a way to generate content once and distribute it across multiple social media services. The content stream score (CSS) measures the breadth of a single content stream by counting the number of transitions between different content formats and platforms. A higher CSS indicates the content reaches a wider audience. Examples are provided of content streams with CSS from 2 to 15 by distributing content from blogs, microblogs, media, livestreams, and aggregates across different social media platforms.
Social Media Patterns 2010 NIM Summit
In this presentation a set of social media patterns that integrate best practices with freely available tools will be discussed. The target audience for this presentation is both the social media strategist and the social media application architect. Social media patterns will provide a foundation upon which an organization can build a rich user experience and also provide the application provider with a rich data set from which the usage habits and preferences can be queried.
Subversion Tech Report (2006)
The document provides an overview of Subversion, an open source version control system. It discusses Subversion's motivation, history, architecture, installation, configuration, conversion from CVS, client usage, and IDE support. The document also addresses deployment considerations and next steps like user account management and training.
julie
The document presents three classical node-link diagrams: a basic node-link diagram showing the relationships between Marites and Alexander Graida and their children Julie Ann, Jheriza, and Jelaine; a nested sets diagram showing the same relationships organized into nested groups; and a layered "icicle" diagram also showing the same family relationships organized into a layered structure.
Licences Libres et Artistes
Diaporama d'accompagnement de la présentation "Licences libres et artistes", lors de l'ArtCamp de Dijon du 28 novembre 2009
AMS Asclepius - Operating Room Visualization
Intuitive Surgery’s introduction of the da Vinci Robotic Surgery System brought 3D visualization to the OR
Ignite Reno #14- What in the Wearable?
Wearable, what does it mean?
personal: clothing, wrist, or in the case of Glass your face
immediacy: augment our daily activities
convenience: look up to read your e-mail
interaction: keyboard and monitor no more
Environment
as we move through our lives the urge is strong to capture the moment
weather it’s an individual, group, community, or social moment
we’re doing it now as the mobile phone with a camera is now standard for personal photography
a camera is a light sensor that can be augmented to capture motion and sound
an opportunity to enhance contextual experience
Viewers also liked (8)
Similar to Patterns in Testing
Implementing TDD in for .net Core applications
This is a presentation I made to make decision on which tools and frameworks should we use in our new dotnet core application to implement test driven development.
Why Unit Testingl
The document discusses various aspects of unit testing including definitions, benefits, naming standards, and best practices. It provides definitions for terms like error, defect, failure. It outlines the benefits of unit testing like finding bugs early, enabling code refactoring. It discusses what should be tested like boundaries, error conditions. It also provides examples of good test names and guidelines for structuring and naming unit tests.
Why unit testingl
The document discusses unit testing and provides guidance on effective unit testing practices. It defines key terms like error, defect, and failure. It outlines the benefits of unit testing like finding defects earlier and maintaining stable code. It discusses naming conventions and frameworks for unit tests. It provides examples of different types of unit tests and guidelines for writing good unit tests that are independent, fast, and test all functionality. The document emphasizes testing boundary conditions and errors as well as documenting test cases.
Why Unit Testingl
The document discusses various aspects of unit testing including definitions, benefits, naming standards, and best practices. It provides definitions for terms like error, defect, failure. It outlines the benefits of unit testing like finding bugs early, enabling code refactoring. It discusses what should be tested like boundaries, error conditions. It also provides examples of good test names and guidelines for structuring and naming unit tests.
Agile Testing Pasadena JUG Aug2009
Automated and agile testing techniques and tools can help teams get software to a "DONE" state. Key aspects include:
- Writing automated unit, integration, and other tests to validate functionality and catch bugs early. This includes techniques like test-driven development.
- Leveraging continuous integration to run tests automatically on each code change to prevent regressions and catch issues quickly.
- Maintaining a balance of test types from unit to acceptance level while focusing on automation to make testing efficient and free up humans for more investigative tasks.
Google test training
The document discusses Google Test, an open source unit testing framework for C++ that can also be used for testing C code, providing an overview of its features and how to implement unit tests using common patterns like test fixtures, assertions, and death tests to validate expected failures. It also covers best practices for writing effective unit tests, including keeping tests independent, focused, and fast-running.
Unit testing php-unit - phing - selenium_v2
The document discusses several automated testing tools:
- PHPUnit is a unit testing framework for PHP that allows writing and running automated tests. It helps ensure code quality and finds regressions.
- Selenium is a suite of tools for automating web application testing across browsers and platforms. It includes the Selenium IDE, RC, and Grid.
- Phing is a build system based on Apache Ant for PHP projects. It uses XML build files and PHP tasks to provide an extensible and flexible build framework.
Unit test Android
Unit testing validates that individual software units perform as designed. Integration testing exposes faults in interactions between integrated units. System testing evaluates a complete system's compliance with requirements. Acceptance testing assesses if a system is acceptable for delivery and meets business needs.
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Learn the strengths and weaknesses of .NET static analysis—and how a comprehensive development testing strategy that also includes unit testing, code review, and runtime error detection can pick up where development testing leaves off.
Unit testing, principles
Unit testing tests individual units of source code to determine if they are fit for use. It is different from integration testing, which combines modules, and validation testing, which checks that a system meets specifications. The goal of unit testing is to isolate and test each part of a program to show that individual parts are correct. Unit testing provides benefits such as finding problems early, facilitating automated testing and change, and improving software quality. Guidelines for effective unit testing include knowing the objective of each test, making tests self-sufficient, ensuring tests are deterministic, following naming conventions, duplicating code for readability, testing results not implementation, and using isolation frameworks.
Software testing methods
The document discusses various software testing methods, including static testing, white box testing, black box testing, unit testing, integration testing, and system testing. It outlines the benefits and pitfalls of each method. For example, static testing can find defects early but is time-consuming, while black box testing tests from a user perspective but may leave code paths untested. The document recommends using a black box approach combined with top-down integration testing, breaking the system into subsystems and assigning specific test responsibilities.
Unit testing & TDD concepts with best practice guidelines.
This article is about software testing. Why do we need testing? What type of tests are there? And we'll talk about the testing levels.
Automated+Testing+Vs+Manual+Testing
Manual testing takes more effort and cost than automated testing. It is more boring and provides limited visibility compared to automated testing. Automated tests can test individual units of code, are reusable, and provide a safety net for refactoring. They also ensure all tests are run, drive clean design, and do not create code clutter like manual tests. However, the initial learning curve and effort to set up automated testing prevents some from adopting it. With proper tooling and process, these barriers can be overcome.
Automated Testing vs Manual Testing
From http://wiki.directi.com/x/AgAa - This is a 24 slide internal presentation covering virtues of Automated Testing vs Manual Testing. Inkeeping with our agile adoption this presentation covers various advantages (11 to be specific) obtained in using TDD and Automated Testing as opposed to Manual Testing
Automated Software Testing Framework Training by Quontra Solutions
Learn through Experience -- We differentiate our training and development program by delivering Role-Based training instead of Product-based training. Ultimately, our goal is to deliver the best IT Training to our clients.
In this training, attendees learn:
Introduction to Automation
• What is automation
• Advantages of automation & Disadvantages of automation
• Different types of Automation Tools
• What to automate in projects
• When to start automation. Scope for automation testing in projects
• About open-source automation tools
Introduction to Selenium
• What is selenium
• Why selenium
• Advantage and Disadvantages of selenium
Selenium components
• Selenium IDE
• Selenium RC
• Selenium WebDriver
• Selenium Grid
Selenium IDE
• Introduction to IDE
• IDE Installation
• Installation and uses of Firepath, Firebug & Debug bar
• Property & value of elements
• Selenium commands
• Assertions & Verification
• Running, pausing and debugging script
• Disadvantages of selenium IDE
• How to convert selenium IDE Scripts into other languages
Locators
• Tools to identify elements/objects
• Firebug
• IE Developer tools
• Google Chrome Developer tools
• Locating elements by ID
• Finding elements by name
• Finding elements by link text
• Finding elements by XPath
• Finding Elements by using CSS
• Summary
Selenium RC
• What is selenium RC
• Advantages of RC, Architecture
• What is Eclipse/IntelliJ, Selenium RC configure with Eclipse/IntelliJ
• Creating, running & debugging RC scripts
Java Concepts
• Introduction to OOPs concepts and Java
• Installation: Java, Eclipse/IntelliJ, selenium, TestNg/JUnit
• operators in java
• Data types in java
• Conditional statements in java
• Looping statements in java
• Output statements in java
• Classes & Objects
• Collection Framework
• Regular Expressions
• Exception Handling
• Packages, Access Specifiers /Modifiers
• String handling
• Log4J for logging
Selenium Web Driver with Java
• Introduction to WebDriver
• Advantages
• Different between RC and WebDriver
• Selenium WebDriver- commands
• Generate scripts in Eclipse/IntelliJ. Run Test Scripts.
• Debugging Test Script
• Database Connections
• Assertions, validations
• Working with Excel
• Pass the data from Excel
• Working with multiple browser
• Window Handling, Alert/confirm & Popup Handling
• Mouse events
• Wait mechanism
• Rich Web Handling: Calendar handing, Auto suggest, Ajax, browser forward/back navigation, keyboard events, certificate handling, event listeners
TestNg/JUnit Framework
• What is TestNg/JUnit
• Integrate the Selenium Scripts and Run from TestNg/JUnit
• Reporting Results and Analysis
• Run Scripts from multiple programs
• Parallel running using TestNg/JUnit
Automation Framework development in Agile testing
• Introduction to Frame W
Automated Unit Testing for Mere Mortals
Automated unit testing involves writing small tests to validate that individual units or components of an application perform as expected. Unit tests should be fast, repeatable, and isolated to test a single function or class. Test doubles like mocks and stubs can stand in for dependencies to make unit tests deterministic. Code coverage metrics measure how much of the code is executed by unit tests, and test-driven development uses tests to drive the design process.
Object Oriented Testing
The document discusses object-oriented testing strategies and techniques. It covers unit testing of individual classes, integration testing of groups of classes, validation testing against requirements, and system testing. Interclass testing focuses on testing collaborations between classes during integration. Test cases should uniquely identify the class under test, state the test purpose and steps, and list expected states, messages, exceptions, and external dependencies.
Paper CS
Automated testing helps identify software bugs earlier through unit testing, code coverage, code analysis, web testing, load testing, and test case management. These tools help ensure software works as intended under normal and peak usage while finding errors. Static code analysis further checks for design, naming, security, and other issues based on configurable rules.
alkatest7
Automated testing helps identify software bugs earlier through unit testing, code coverage, code analysis, web testing, load testing, and test case management. These tools help ensure software quality by finding defects early in development and validating that code works as intended under normal and peak loads. Static code analysis further helps enforce coding standards and reduces code reviews. Together, these automated testing practices help reduce software defects and associated economic costs.
justin presentation upload PPT june 19
Automated testing helps identify software bugs earlier through unit testing, code coverage, code analysis, web testing, load testing, and test case management. These tools help ensure software quality by finding defects early in development and validating that code performs as expected under normal and peak loads. Static code analysis further helps enforce coding standards and reduces code reviews. Together, these automated testing practices can help eliminate an estimated $22.2 billion in costs annually from software defects in the US economy.
Similar to Patterns in Testing (20)
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Beyond Static Analysis: Integrating .NET Static Analysis with Unit Testing a...
Unit testing & TDD concepts with best practice guidelines.
Unit testing & TDD concepts with best practice guidelines.
Automated Software Testing Framework Training by Quontra Solutions
Automated Software Testing Framework Training by Quontra Solutions
Recently uploaded
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
AWS Cloud Cost Optimization Presentation.pptx
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
This case study explores designing a scalable e-commerce platform, covering key requirements, system components, and best practices.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Predictive maintenance is a proactive approach that anticipates equipment failures before they happen. At the forefront of this innovative strategy is Artificial Intelligence (AI), which brings unprecedented precision and efficiency. AI in predictive maintenance is transforming industries by reducing downtime, minimizing costs, and enhancing productivity.
Digital Marketing Trends in 2024 | Guide for Staying Ahead
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Recently uploaded (20)
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
System Design Case Study: Building a Scalable E-Commerce Platform - Hiike
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
leewayhertz.com-AI in predictive maintenance Use cases technologies benefits ...
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Patterns in Testing
- 1. for Code, Components and Systems Patterns In Testing
- 2. overview Why write tests? Purist vs. Practitioner New Code vs. Legacy Code Unit Testing Functional Testing User Driven Testing Test Automation Ecosystem 5/20/2010 Presented by Joe Chavez
- 3. Why write tests? 5/20/2010 Presented by Joe Chavez Catch defects during implementation Software testing is not the same as hardware testing More moving parts Documentation is often stale or non-existent Tests provide opportunity to document the intent of a class, component or system with working code Once written, tests are repeatable with very little overhead Test help a team maintain and more importantly change code with reduced risk Software tests can drive hardware testing Automated tools cannot capture the intent of the code – especially dynamic intent These tools complement the coding of tests, not replace
- 4. PURIST vs. Practitioner 5/20/2010 Presented by Joe Chavez
- 5. PURIST vs. Practitioner Balance achieved with Pragmatism Context is key Type of code: new, legacy, generated, etc. Robustness of tools Complexity of design Developer skillset Management support Perception is often that writing test code is not contributing to the bottom line Reality a few tests now can save time during the integration/delivery phases of a project 5/20/2010 Presented by Joe Chavez
- 6. New Code vs. Legacy Code New Code Can benefit greatly from a Test Driven approach Identify critical areas in the requirements/design that deliver most value Typically can use the best of breed testing tools & frameworks Legacy Code Improve – White box with Test Driven approach Incorporate – Characterize actual behavior in isolation Rewrite – Analyze existing code and write tests as part of new code Pair programming is helpful Can work in code review mode while writing tests Ideal situation: original programmer is part of the pair 5/20/2010 Presented by Joe Chavez
- 7. New Code vs. Legacy Code Special Cases: Open Source Usually come with a test suite – use caution if there is no test suite Generated Code For C/C++ - characterize memory management Explore usage of generated code through writing tests 5/20/2010 Presented by Joe Chavez
- 8. Unit Testing Single Purpose Testing Focused on public methods of a class View through the caller eyes Typically one (1) assertion check for pass/fail Code scenarios to verify correct behavior under normal and abusive conditions Testing Frameworks C# - NUnit C++ - UnitTest++ Java – jUnit Mocking Frameworks 5/20/2010 Presented by Joe Chavez
- 9. Functional Testing Verify the integration of several components and/or classes Use same testing framework that unit tests use Good for integration testing new/legacy/open source/generated code Verification scenarios Data flow between components Actual vs. expected results at each stage Use case scenarios 5/20/2010 Presented by Joe Chavez
- 10. USER Driven Testing Data Driven System A system that can be configured for execution based on an input data set and will produced an expected set of output data Test Application May require development of a test application – typically a console application Accepts file based input and/or command line options Produces file based output 5/20/2010 Presented by Joe Chavez
- 11. Test Automation Run tests early and often Integrate into the development/build process Visual Studio post build event msbuild/ant/make scripts Continuous Integration support Silent success and error on failure If all tests succeed then report silently (X number of test passed) If any test fails then fail the build Report failed test with a context (i.e. failed assertion, stack trace) Take corrective action before moving on 5/20/2010 Presented by Joe Chavez
- 12. IN CONTEXT 5/20/2010 Presented by Joe Chavez