Test Driven Development: Part 2
•Download as ODP, PDF•
0 likes•2,768 views
The document discusses test driven development (TDD) and its history and benefits. TDD involves writing automated tests before writing code to make sure it passes the tests, eliminating bugs. It originated from Toyota's "just in time" manufacturing model and helps reduce waste and defects compared to traditional waterfall development approaches. The document demonstrates TDD with a live coding example and provides resources for learning more.
Report
Share
Report
Share
Recommended
How to Deliver the Right Software (Specification by example)
Talk about Specification by Example. What's the problems it tries to tackle and how to solve them.
I gave this talk at findmypast.com on a "lunch and learn" weekly meeting for the company.
This is a new version of my previous presentation about "Specification by example"
http://www.slideshare.net/AsierBarrenetxea1/specification-by-example-33594438
How to be proud when you are done
Although all of us speak the same language, each of us uses different meaning of words "soon”, "fine” and "done”. That’s why for one developer "I’m done” means that just a moment ago the part of the code with implemented functionality has been successfully executed, while for another developer it means that code has been committed to repository but without checking if build is green or not on continuous integration server. At the same time "done" of developer-perfectionist means totally refactored and optimized code. And only for "black swan”-developer phrase "I'm done“ means that all tests were passed, new functionality was documented on wiki and a new feature was verified by customer on the demo server.
So if you want to decrease a risk of misunderstanding inside a team or between team and customer you should make agreement about common vision of “definition of done“ and then start using it on a daily basis. In order to prevent losing your time and stepping on the hidden rake during discussion of your done criteria we will share our knowledge about creating compact and most effective “definition of done“. We will talk about lifecycle of this document and about approaches that help you to add important items to it. We will discuss doneness on different levels (preplanning, user story and task development, sprint). And of course we won’t forget to tell you how to create “Definition of Done“ which will satisfy not only your team but your customer as well.
XP Injection
Nikolay Alimenkou and Aleksey Solntsev will show how to migrate from Ant project to Maven2 project and start using full power of XP engineering practices: CI, TDD, refactoring.
Code review
This document discusses how to improve software quality through code reviews. It begins by stating the goals of code review, such as improving code quality, sharing knowledge, and educating developers. It then discusses classification of code reviews from less to more formal. The document outlines some best practices for code reviews, including having a reviewer and author, choosing reviewers strategically, and driving the review in different ways. It provides answers to common questions about organizing effective code reviews and leaves with tips, such as tracking reviewers, using checklists, and ensuring comfortable conditions for all.
Test Driven Development
Testing is not something that traditional PHP developers are being familiar with. This session introduces the needs and means for testing, and the test-driven development model to create rock-solid PHP applications.
Bringing Quality Design Systems to Life with Storybook & Applitools
** Full webinar recording: https://youtu.be/R6WnEzlMHac **
Bringing design systems and component libraries to life can be a large, challenging process without the right tools. On top of that, maintaining a high level of quality throughout those systems brings its own challenge.
While there’s no shortage of ways to manually create a design system from scratch, doing so can be time consuming and can lead to technical debt when the system itself isn’t itself in a structure.
Storybook is a tool for developers that helps bring design systems and component libraries to life, providing structured tooling and a web dashboard. It gives those developers, and even designers, a way to focus on each individual component while being able to see the system from a higher perspective.
On top of that, Applitools is an automated Visual Testing solution that easily stacks right on top of Storybook with the Storybook Eyes SDK. With a single command, Applitools provides full test coverage for each component of your design system.
Join Developer Advocate, Colby Fayock, as he walks through:
How to take advantage of using Storybook to build scalable design systems
How Applitools makes automating the testing of those components easy
How to focus on building great experiences while automating quality checks with visual testing
Developers Border Line: Unit Testing
Unit testing involves developers writing short tests of individual units or modules of code as they develop software. These tests automatically validate that each piece of the software performs as intended. Benefits of unit testing include finding bugs earlier, simplifying integration, facilitating change, and encouraging good design. Developers should write tests early and often, refactor code frequently to keep it simple, and fix bugs as soon as they are discovered. Checklists can help ensure unit tests cover important functionality.
Continuous, continuous, continuous
An introduction on Continuous Delivery (CD) and related practices to delivery high quality software faster
Recommended
How to Deliver the Right Software (Specification by example)
Talk about Specification by Example. What's the problems it tries to tackle and how to solve them.
I gave this talk at findmypast.com on a "lunch and learn" weekly meeting for the company.
This is a new version of my previous presentation about "Specification by example"
http://www.slideshare.net/AsierBarrenetxea1/specification-by-example-33594438
How to be proud when you are done
Although all of us speak the same language, each of us uses different meaning of words "soon”, "fine” and "done”. That’s why for one developer "I’m done” means that just a moment ago the part of the code with implemented functionality has been successfully executed, while for another developer it means that code has been committed to repository but without checking if build is green or not on continuous integration server. At the same time "done" of developer-perfectionist means totally refactored and optimized code. And only for "black swan”-developer phrase "I'm done“ means that all tests were passed, new functionality was documented on wiki and a new feature was verified by customer on the demo server.
So if you want to decrease a risk of misunderstanding inside a team or between team and customer you should make agreement about common vision of “definition of done“ and then start using it on a daily basis. In order to prevent losing your time and stepping on the hidden rake during discussion of your done criteria we will share our knowledge about creating compact and most effective “definition of done“. We will talk about lifecycle of this document and about approaches that help you to add important items to it. We will discuss doneness on different levels (preplanning, user story and task development, sprint). And of course we won’t forget to tell you how to create “Definition of Done“ which will satisfy not only your team but your customer as well.
XP Injection
Nikolay Alimenkou and Aleksey Solntsev will show how to migrate from Ant project to Maven2 project and start using full power of XP engineering practices: CI, TDD, refactoring.
Code review
This document discusses how to improve software quality through code reviews. It begins by stating the goals of code review, such as improving code quality, sharing knowledge, and educating developers. It then discusses classification of code reviews from less to more formal. The document outlines some best practices for code reviews, including having a reviewer and author, choosing reviewers strategically, and driving the review in different ways. It provides answers to common questions about organizing effective code reviews and leaves with tips, such as tracking reviewers, using checklists, and ensuring comfortable conditions for all.
Test Driven Development
Testing is not something that traditional PHP developers are being familiar with. This session introduces the needs and means for testing, and the test-driven development model to create rock-solid PHP applications.
Bringing Quality Design Systems to Life with Storybook & Applitools
** Full webinar recording: https://youtu.be/R6WnEzlMHac **
Bringing design systems and component libraries to life can be a large, challenging process without the right tools. On top of that, maintaining a high level of quality throughout those systems brings its own challenge.
While there’s no shortage of ways to manually create a design system from scratch, doing so can be time consuming and can lead to technical debt when the system itself isn’t itself in a structure.
Storybook is a tool for developers that helps bring design systems and component libraries to life, providing structured tooling and a web dashboard. It gives those developers, and even designers, a way to focus on each individual component while being able to see the system from a higher perspective.
On top of that, Applitools is an automated Visual Testing solution that easily stacks right on top of Storybook with the Storybook Eyes SDK. With a single command, Applitools provides full test coverage for each component of your design system.
Join Developer Advocate, Colby Fayock, as he walks through:
How to take advantage of using Storybook to build scalable design systems
How Applitools makes automating the testing of those components easy
How to focus on building great experiences while automating quality checks with visual testing
Developers Border Line: Unit Testing
Unit testing involves developers writing short tests of individual units or modules of code as they develop software. These tests automatically validate that each piece of the software performs as intended. Benefits of unit testing include finding bugs earlier, simplifying integration, facilitating change, and encouraging good design. Developers should write tests early and often, refactor code frequently to keep it simple, and fix bugs as soon as they are discovered. Checklists can help ensure unit tests cover important functionality.
Continuous, continuous, continuous
An introduction on Continuous Delivery (CD) and related practices to delivery high quality software faster
How selenium can transform your qa career
This document discusses how learning the test automation tool Selenium can transform a QA professional's career. It begins by defining test automation and discussing why and when tests should be automated. It addresses common myths around test automation, comparing automated and manual testing. The document then discusses Selenium specifically, clarifying myths and truths about it. It considers different types of learners who might learn Selenium and how it could help with jobs, promotions, and project costs. Finally, it addresses common fears around learning to code with Selenium and provides recommendations on what to learn.
Managing technical debt - Dan Nicola - Florin Cardasim
This document discusses various types of technical debt that can accumulate in software projects, including code debt, architectural debt, test debt, and knowledge debt. It notes that technical debt can lead to lower productivity, higher support costs, more bugs and patches, and unhappy customers and stakeholders. The document provides examples of comments that indicate the presence of technical debt and offers approaches for managing technical debt, such as covering code with tests before refactoring, making code more modular and extensible, and conducting purely technical releases to improve code quality. It discusses different strategies for addressing technical debt through repayment, conversion, or just paying interest and concludes that while technical debt is unavoidable, it is not always bad and is often more of a cultural issue than
Testing Hourglass at Jira Frontend - by Alexey Shpakov, Sr. Developer @ Atlas...
Alexey Shpakov presents on testing in Jira Frontend. He discusses the testing pyramid with unit, integration, and end-to-end tests. He then introduces the concept of a "testing hourglass" which adds deployment and post-deployment verification to the pyramid. Key aspects of each type of test are discussed such as using feature flags, monitoring for flaky tests, and gradual rollouts to reduce risk.
Justin Ison
The document discusses automating exploratory testing by creating an app crawler that can emulate user interactions, test across different platforms, languages, resolutions and orientations. Some key points:
- Automated exploratory testing is needed due to shorter release cycles and less manual testing time.
- The author created an app crawler that can capture elements, images, errors, exceptions, performance data and replay tests across platforms.
- Challenges include handling authentication, detecting unique locators, and rescuing apps that get stuck.
- The crawler detects languages, monitors logs and exceptions, and uses Applitools for image validation to further automate the process.
- The goal is to help fill quality gaps
Phoenix User Group Slides
The document summarizes key aspects of an Agile development process used by Brightspark, a Toronto-based technology company founded in 1999. It highlights two major benefits of Agile as transparency and regular delivery of working software. It also discusses two major risks as churn and technical debt, and how practices like test-driven development, continuous integration, and refactoring help mitigate these risks.
Agile Testing Dilemmas
Based on hands-on Agile experience acquired over multiple delivery projects and Agile coaching/consulting assignments, Vatsala and Aman share common Agile Testing dilemmas, and possible solutions, tying them to the principle of "moving testing upstream".
Presented at Next Generation Testing conference in Bangalore, India (July 2014).
ISTQB Foundation and Selenium Java Automation Testing
This document provides an overview and summary of an ISTQB Foundation and Selenium Java Automation Testing course. The course covers ISTQB certification based professional training using the 2018 syllabus, as well as test automation using Selenium Java and .NET frameworks. It is designed to help students learn software testing skills and prepare for careers as test analysts or test automation engineers. Key topics include dynamic testing techniques, testing throughout the software development lifecycle, component testing, test management, and static testing. The course also provides hands-on training in test automation using Selenium WebDriver, building reusable automation components, cross-browser testing, and XSLT reporting.
Continuous integration
Continuous integration (CI) aims to improve software quality and reduce delivery time by implementing continuous quality control processes like running automated unit, integration, and acceptance tests. CI helps teams be more efficient by quickly identifying issues and getting feedback. Key principles of CI include having a single code repository, automating builds and testing, publishing the latest build daily, and getting builds into production to enable fast feedback. Automating builds is important to ensure consistency across environments and allow issues to be identified and addressed early during development rather than in production.
Specification by example and agile acceptance testing
Specification by example and agile acceptance testing, presentation given to HSBC developers on 21/09/09 for more info see http://specificationbyexample.com
Spec by-example
Specification by example is a technique that has the following key benefits: less rework, higher product quality, more efficient implementation of changes, and better alignment across roles. It involves deriving system scope from goals, specifying collaboratively using examples, refining the specification, and automating validation to evolve a living documentation system. The document discusses practices for each step, including deriving requirements from goals by asking "why", using workshops and examples to specify collaboratively, refining specifications through iteration, and automating tests from examples to continuously validate the system.
What a DevOps specialist has to know about static code analysis
Reasons of failed introductions.
Place of static analysis in the DevOps process.
Static analysis – friend or foe.
Notifications about analysis results.
What to do with 10 000 analyzer warnings after the first run?
How much time is needed for fixing all bugs?
Q&A or what’s next?
Zero to tested
The document discusses strategies for improving test automation in challenging environments. It advocates for automating infrastructure provisioning using tools like Chef, Packer, Terraform and AWS to create ephemeral, automated environments. It also recommends building test code that is resilient to flakiness through techniques like retry logic, explicit waits, and logging/detecting non-determinism. The document provides a code example demonstrating how to automate infrastructure, write tests that can handle asynchronicity and other challenges, and effectively report failures to drive improvement.
Adam carmi
This document discusses automating visual software testing. It begins by explaining that visual testing is used to verify a graphical user interface appears correctly. It then discusses why visual testing should be automated, such as because the test matrix is too large to cover manually across different browsers, devices, resolutions, etc. It also notes that mobile app quality is critical so testing needs to be thorough. The document outlines how visual testing works by taking screenshots, comparing them to baselines, and reporting differences. It provides examples of tools that can be used for visual testing and discusses how tests can be integrated into development pipelines from the code level through production.
Product Vs Craft
This document summarizes a talk given by Juan Delgado on the topics of product vs craft in software development. Some key points made in the document include:
- The quality and practices used in software development should be adapted based on the vision and goals of the product as well as where the product is in its lifecycle. Extreme quality may not be necessary early on.
- There is no single "right" way to build software - different approaches can both be appropriate depending on the context and needs of the product and business. Quality is contextual.
- Software teams should aim to implement "enough quality" - quality that allows for correctness and the ability to continue developing the product, but not necessarily perfect or extreme quality
Test Driven Development
The document discusses a meetup about unit testing on the Android platform. It provides an overview of objectives which are to understand basics of unit testing, create a unit test, and run it on an emulator. It discusses benefits of unit testing such as reducing issues during development and maintenance by facilitating change, simplifying integration, and serving as documentation. It also notes that while more code is written during development with testing, it allows for confidence in refactoring and determining if original functions still work with changes. The meetup aims to demonstrate testing on Android.
Selenium as a trend
The document summarizes some key points about using Selenium for test automation:
1. Common traps to avoid include choosing Selenium solely based on trends, automating all tests without consideration for test types, and initiating automation late in the development cycle.
2. An example project story describes using Selenium with Java, Jenkins, and a page object pattern for tests of a PHP ecommerce site.
3. Issues that can arise include tests becoming difficult to maintain over time and new features breaking many existing tests. This leads to wasted effort and unhappy stakeholders.
Test Driven Development
Test Driven Development (TDD) provides several benefits over traditional waterfall and iterative development models:
1) It establishes a fast feedback cycle between writing code and writing tests, allowing developers to quickly validate functionality.
2) The automated tests that are written serve as documentation and specifications for the code, giving confidence that changes don't break existing functionality.
3) High test coverage promotes well-designed, loosely-coupled code that is easier to maintain and extend over time.
Offshore tips sharing_2.0
This document provides tips for effectively managing software projects, including meeting preparation, requirements analysis, issue handling, and delivery. It emphasizes preparing meeting agendas in advance, clearly communicating, thoroughly understanding requirements, promptly reporting serious issues, and providing detailed instructions to ensure smooth delivery. Examples are given of past issues that could have been avoided with better application of these tips. The goal is to apply even basic practices more strictly to improve quality.
What Software Quality Assurance Means to Me
Software quality assurance means delivering useful features one at a time through a test-first methodology. Test-driven development gives confidence to experiment and serves as a benchmark for classes, with unit tests serving as regression tests. It allows senior developers to hand functional tests to junior developers to implement, focusing on outcomes over specific implementations. Both internal and external quality are important, with ambiguous APIs hindering productivity. Good development involves collaboration, even for solo projects, and smoke tests should always be run before sharing code with others.
Test Driven Development
Test-driven development allows developers to find and fix bugs more quickly by writing automated tests before developing code. This reduces debugging time and improves productivity. Constant testing is crucial for short release cycles and gives developers confidence to refactor and improve code quality throughout development. Automated testing enables developers to test thoroughly without losing focus.
Why Code 'for' Android and Motodev Studio
This document discusses the growing popularity of Android smartphones and opportunities for developers. It notes that smartphone sales increased 27% in the second quarter while overall phone sales declined 6%. Several Android phone models like the HTC Magic and Samsung Galaxy have sold over a million and 100,000 units respectively. The document projects Android phone sales could reach over 2.7 million units by the end of the year as more phones and carriers adopt the Android platform. It highlights the MOTODEV Studio Beta as a new tool to support Android development on Motorola phones.
Swisstrains.ch: Present, past and future
- Today: A demonstration of a real-time vehicle tracking system from 2011 using data from 2007-2011.
- Past: The system has evolved from using text files in the 90s to relational databases in 2007-2008 and Fusion Tables in 2010. Graphics and data integration tools have also improved.
- Future: Potential next steps include expanding to more cities, using open data, improving the website swisstrains.ch, integrating newer APIs, and developing more complex simulations.
More Related Content
What's hot
How selenium can transform your qa career
This document discusses how learning the test automation tool Selenium can transform a QA professional's career. It begins by defining test automation and discussing why and when tests should be automated. It addresses common myths around test automation, comparing automated and manual testing. The document then discusses Selenium specifically, clarifying myths and truths about it. It considers different types of learners who might learn Selenium and how it could help with jobs, promotions, and project costs. Finally, it addresses common fears around learning to code with Selenium and provides recommendations on what to learn.
Managing technical debt - Dan Nicola - Florin Cardasim
This document discusses various types of technical debt that can accumulate in software projects, including code debt, architectural debt, test debt, and knowledge debt. It notes that technical debt can lead to lower productivity, higher support costs, more bugs and patches, and unhappy customers and stakeholders. The document provides examples of comments that indicate the presence of technical debt and offers approaches for managing technical debt, such as covering code with tests before refactoring, making code more modular and extensible, and conducting purely technical releases to improve code quality. It discusses different strategies for addressing technical debt through repayment, conversion, or just paying interest and concludes that while technical debt is unavoidable, it is not always bad and is often more of a cultural issue than
Testing Hourglass at Jira Frontend - by Alexey Shpakov, Sr. Developer @ Atlas...
Alexey Shpakov presents on testing in Jira Frontend. He discusses the testing pyramid with unit, integration, and end-to-end tests. He then introduces the concept of a "testing hourglass" which adds deployment and post-deployment verification to the pyramid. Key aspects of each type of test are discussed such as using feature flags, monitoring for flaky tests, and gradual rollouts to reduce risk.
Justin Ison
The document discusses automating exploratory testing by creating an app crawler that can emulate user interactions, test across different platforms, languages, resolutions and orientations. Some key points:
- Automated exploratory testing is needed due to shorter release cycles and less manual testing time.
- The author created an app crawler that can capture elements, images, errors, exceptions, performance data and replay tests across platforms.
- Challenges include handling authentication, detecting unique locators, and rescuing apps that get stuck.
- The crawler detects languages, monitors logs and exceptions, and uses Applitools for image validation to further automate the process.
- The goal is to help fill quality gaps
Phoenix User Group Slides
The document summarizes key aspects of an Agile development process used by Brightspark, a Toronto-based technology company founded in 1999. It highlights two major benefits of Agile as transparency and regular delivery of working software. It also discusses two major risks as churn and technical debt, and how practices like test-driven development, continuous integration, and refactoring help mitigate these risks.
Agile Testing Dilemmas
Based on hands-on Agile experience acquired over multiple delivery projects and Agile coaching/consulting assignments, Vatsala and Aman share common Agile Testing dilemmas, and possible solutions, tying them to the principle of "moving testing upstream".
Presented at Next Generation Testing conference in Bangalore, India (July 2014).
ISTQB Foundation and Selenium Java Automation Testing
This document provides an overview and summary of an ISTQB Foundation and Selenium Java Automation Testing course. The course covers ISTQB certification based professional training using the 2018 syllabus, as well as test automation using Selenium Java and .NET frameworks. It is designed to help students learn software testing skills and prepare for careers as test analysts or test automation engineers. Key topics include dynamic testing techniques, testing throughout the software development lifecycle, component testing, test management, and static testing. The course also provides hands-on training in test automation using Selenium WebDriver, building reusable automation components, cross-browser testing, and XSLT reporting.
Continuous integration
Continuous integration (CI) aims to improve software quality and reduce delivery time by implementing continuous quality control processes like running automated unit, integration, and acceptance tests. CI helps teams be more efficient by quickly identifying issues and getting feedback. Key principles of CI include having a single code repository, automating builds and testing, publishing the latest build daily, and getting builds into production to enable fast feedback. Automating builds is important to ensure consistency across environments and allow issues to be identified and addressed early during development rather than in production.
Specification by example and agile acceptance testing
Specification by example and agile acceptance testing, presentation given to HSBC developers on 21/09/09 for more info see http://specificationbyexample.com
Spec by-example
Specification by example is a technique that has the following key benefits: less rework, higher product quality, more efficient implementation of changes, and better alignment across roles. It involves deriving system scope from goals, specifying collaboratively using examples, refining the specification, and automating validation to evolve a living documentation system. The document discusses practices for each step, including deriving requirements from goals by asking "why", using workshops and examples to specify collaboratively, refining specifications through iteration, and automating tests from examples to continuously validate the system.
What a DevOps specialist has to know about static code analysis
Reasons of failed introductions.
Place of static analysis in the DevOps process.
Static analysis – friend or foe.
Notifications about analysis results.
What to do with 10 000 analyzer warnings after the first run?
How much time is needed for fixing all bugs?
Q&A or what’s next?
Zero to tested
The document discusses strategies for improving test automation in challenging environments. It advocates for automating infrastructure provisioning using tools like Chef, Packer, Terraform and AWS to create ephemeral, automated environments. It also recommends building test code that is resilient to flakiness through techniques like retry logic, explicit waits, and logging/detecting non-determinism. The document provides a code example demonstrating how to automate infrastructure, write tests that can handle asynchronicity and other challenges, and effectively report failures to drive improvement.
Adam carmi
This document discusses automating visual software testing. It begins by explaining that visual testing is used to verify a graphical user interface appears correctly. It then discusses why visual testing should be automated, such as because the test matrix is too large to cover manually across different browsers, devices, resolutions, etc. It also notes that mobile app quality is critical so testing needs to be thorough. The document outlines how visual testing works by taking screenshots, comparing them to baselines, and reporting differences. It provides examples of tools that can be used for visual testing and discusses how tests can be integrated into development pipelines from the code level through production.
Product Vs Craft
This document summarizes a talk given by Juan Delgado on the topics of product vs craft in software development. Some key points made in the document include:
- The quality and practices used in software development should be adapted based on the vision and goals of the product as well as where the product is in its lifecycle. Extreme quality may not be necessary early on.
- There is no single "right" way to build software - different approaches can both be appropriate depending on the context and needs of the product and business. Quality is contextual.
- Software teams should aim to implement "enough quality" - quality that allows for correctness and the ability to continue developing the product, but not necessarily perfect or extreme quality
Test Driven Development
The document discusses a meetup about unit testing on the Android platform. It provides an overview of objectives which are to understand basics of unit testing, create a unit test, and run it on an emulator. It discusses benefits of unit testing such as reducing issues during development and maintenance by facilitating change, simplifying integration, and serving as documentation. It also notes that while more code is written during development with testing, it allows for confidence in refactoring and determining if original functions still work with changes. The meetup aims to demonstrate testing on Android.
Selenium as a trend
The document summarizes some key points about using Selenium for test automation:
1. Common traps to avoid include choosing Selenium solely based on trends, automating all tests without consideration for test types, and initiating automation late in the development cycle.
2. An example project story describes using Selenium with Java, Jenkins, and a page object pattern for tests of a PHP ecommerce site.
3. Issues that can arise include tests becoming difficult to maintain over time and new features breaking many existing tests. This leads to wasted effort and unhappy stakeholders.
Test Driven Development
Test Driven Development (TDD) provides several benefits over traditional waterfall and iterative development models:
1) It establishes a fast feedback cycle between writing code and writing tests, allowing developers to quickly validate functionality.
2) The automated tests that are written serve as documentation and specifications for the code, giving confidence that changes don't break existing functionality.
3) High test coverage promotes well-designed, loosely-coupled code that is easier to maintain and extend over time.
Offshore tips sharing_2.0
This document provides tips for effectively managing software projects, including meeting preparation, requirements analysis, issue handling, and delivery. It emphasizes preparing meeting agendas in advance, clearly communicating, thoroughly understanding requirements, promptly reporting serious issues, and providing detailed instructions to ensure smooth delivery. Examples are given of past issues that could have been avoided with better application of these tips. The goal is to apply even basic practices more strictly to improve quality.
What Software Quality Assurance Means to Me
Software quality assurance means delivering useful features one at a time through a test-first methodology. Test-driven development gives confidence to experiment and serves as a benchmark for classes, with unit tests serving as regression tests. It allows senior developers to hand functional tests to junior developers to implement, focusing on outcomes over specific implementations. Both internal and external quality are important, with ambiguous APIs hindering productivity. Good development involves collaboration, even for solo projects, and smoke tests should always be run before sharing code with others.
Test Driven Development
Test-driven development allows developers to find and fix bugs more quickly by writing automated tests before developing code. This reduces debugging time and improves productivity. Constant testing is crucial for short release cycles and gives developers confidence to refactor and improve code quality throughout development. Automated testing enables developers to test thoroughly without losing focus.
What's hot (20)
Managing technical debt - Dan Nicola - Florin Cardasim
Managing technical debt - Dan Nicola - Florin Cardasim
Testing Hourglass at Jira Frontend - by Alexey Shpakov, Sr. Developer @ Atlas...
Testing Hourglass at Jira Frontend - by Alexey Shpakov, Sr. Developer @ Atlas...
ISTQB Foundation and Selenium Java Automation Testing
ISTQB Foundation and Selenium Java Automation Testing
Specification by example and agile acceptance testing
Specification by example and agile acceptance testing
What a DevOps specialist has to know about static code analysis
What a DevOps specialist has to know about static code analysis
Viewers also liked
Why Code 'for' Android and Motodev Studio
This document discusses the growing popularity of Android smartphones and opportunities for developers. It notes that smartphone sales increased 27% in the second quarter while overall phone sales declined 6%. Several Android phone models like the HTC Magic and Samsung Galaxy have sold over a million and 100,000 units respectively. The document projects Android phone sales could reach over 2.7 million units by the end of the year as more phones and carriers adopt the Android platform. It highlights the MOTODEV Studio Beta as a new tool to support Android development on Motorola phones.
Swisstrains.ch: Present, past and future
- Today: A demonstration of a real-time vehicle tracking system from 2011 using data from 2007-2011.
- Past: The system has evolved from using text files in the 90s to relational databases in 2007-2008 and Fusion Tables in 2010. Graphics and data integration tools have also improved.
- Future: Potential next steps include expanding to more cities, using open data, improving the website swisstrains.ch, integrating newer APIs, and developing more complex simulations.
Introduction to Canvas
The document discusses the basics of using the Canvas class in Android development. Canvas allows for control over visual effects and unique animations. It allows drawing images, shapes, text, and bitmaps and handling user input events. Questions about Canvas usage are welcome.
CodeAndroid Meet Up Slides - Augmented Reality on Android
This document summarizes an Android developer meetup hosted by CodeAndroid.org. The agenda included presentations on building augmented reality apps for Android, building an Android app in 30 minutes, and a Q&A with the winner of an Android app challenge. The meetup was intended to promote Android development and provide information about what developers can build for the Android platform.
Mobile Device APIs
Thoughts on the past, present and future of device APIs for (mostly mobile) web developers. NB: is probably out of date already.
Rehnquist William H (2004) Judicial Independence Dedicated to Chief Justice H...
Rehnquist William H (2004) Judicial Independence Dedicated to Chief Justice H...Global Currency News Including the Iraqi Dinar
1) The Chief Justice discusses the importance of judicial independence by comparing the American and French experiences after adopting declarations of rights. While the language was similar, France lacked an independent judiciary and descended into the Reign of Terror without enforcing individual rights.
2) He outlines two significant early challenges to the independence of the US judiciary - the impeachment of Judge John Pickering for political reasons along party lines, and the impeachment of Justice Samuel Chase in an attempt to exert political control over the Supreme Court.
3) The impeachment of Justice Samuel Chase in 1805 for his partisan actions from the bench became a major test of judicial independence, with his trial before the Senate gaining significant public interest.Android Framework
The document summarizes an Android meetup event that took place on May 25th 2009. The agenda included talks on Android frameworks, intents, broadcast receivers, test driven development, and Bluetooth app development. The event was hosted by CodeAndroid, a local Android developer group, and supported by Google and HTC Singapore. Attendees learned about key Android concepts like activities and their lifecycles, as well as tools and techniques for building Android apps.
10 tips to get started with html5 games
This document provides 10 tips for developing HTML5 games for both desktop and mobile platforms. Some key points covered include using the <canvas> tag for games, touch events for mobile, dirty rectangles to improve framerate on mobile, matching button sizes to fingers, using localStorage to save game data, and tools for debugging mobile games. More details on these techniques and HTML5 game development can be found at the listed web addresses.
Android: Intent, Intent Filter, Broadcast Receivers
1) Intents represent requests for actions to be performed, while Intent Filters register which app components can handle certain actions and types of data.
2) Broadcast receivers listen for broadcast intents and allow interaction between app components.
3) Intents are used to start activities, broadcast messages, and launch other apps like the Android Market. Intent Filters are required for intent resolution and matching intents to the correct components.
Cross platform mobile web apps
The document discusses the state of cross-platform mobile web apps. It notes that while HTML5 provides many capabilities of native mobile apps, developing cross-platform web apps remains challenging due to differences in browser platforms and a lack of universal support for HTML5 features. Hybrid mobile apps that use a native wrapper and HTML5 for app logic offer greater access to device functionality but still must target multiple platforms. Ultimately, no solution provides the same level of "nativeness" as truly native mobile apps.
Viewers also liked (11)
CodeAndroid Meet Up Slides - Augmented Reality on Android
CodeAndroid Meet Up Slides - Augmented Reality on Android
Rehnquist William H (2004) Judicial Independence Dedicated to Chief Justice H...
Rehnquist William H (2004) Judicial Independence Dedicated to Chief Justice H...
Android: Intent, Intent Filter, Broadcast Receivers
Android: Intent, Intent Filter, Broadcast Receivers
Similar to Test Driven Development: Part 2
Introducing Continuous Integration Using Vsts
A presentation I gave about Continuous Integration and it's role in the software development life cycle with some of my real life experiences.
Software Development Standard Operating Procedure
This is a sample SOP document that we are using in our company which has helped us improve the quality of output immensely
Agile Methodologies And Extreme Programming
The document discusses Agile development and Extreme Programming (XP). It provides an overview of 12 key practices of XP, including planning games, small releases, test-driven development, pair programming, collective ownership, continuous integration and 40-hour work weeks. It also discusses how XP aims to solve software engineering problems through intensive teamwork, handling changes and staff turnover, and involving customers.
Agile Methodologies And Extreme Programming - Svetlin Nakov
1. Agile development and Extreme Programming (XP) are methodologies that focus on iterative development, collaboration, and adaptability.
2. XP consists of 12 key practices including simple design, test-driven development, pair programming, and small releases. It aims to improve quality, reduce risks, and adapt to changing requirements.
3. While XP works well for some projects and teams, its practices may not be suitable or flexible enough for all situations. Developers should understand the principles behind XP and tailor practices as needed for their specific projects.
Extreme Programming Talk Wise Consulting Www.Talkwiseconsulting
eXtreme Programming (XP) is an agile software development methodology that aims to improve quality and responsiveness to changing requirements. It consists of values like communication, simplicity, feedback and courage, as well as practices like planning, small releases, testing, pair programming and refactoring. XP attempts to address common software project problems like schedule slips, defects, and inability to adapt to changing business needs. It advocates short iterations, frequent integration and customer feedback to deliver working, tested software rapidly and allow requirements to evolve over time at low cost.
Extreme programming talk wise consulting - www.talkwiseconsulting
eXtreme Programming (XP) is an agile software development methodology that focuses on rapid software development and delivery through practices like continuous integration, pair programming, and frequent refactoring. It aims to address common software project problems like schedule slips, high defect rates, and changing requirements by having short development cycles, automated testing, and close collaboration between developers and customers. Key XP practices include planning game, small releases, simple design, testing, refactoring, pair programming, and on-site customer involvement. Adopting XP can benefit both developers through better requirements and technical empowerment, and customers through timely delivery of valuable software that can adapt to changes.
Tales of modernizing trello's web stack
The web community is a fast moving community and over the recent years, many great frameworks and tools have emerged. Technology changes made in the past are not always the right ones today. This applies to Trello’s web stack too. CoffeeScript and Backbone were great choices 7 years ago but there are better tools and frameworks available now, so the Trello team decided to update its stack. But, how does one tackle this and how do you make sure you continue to innovate product-wise while modernizing its web stack? This is what we will discuss in this session -- main drivers for modernizing, the reasoning for choosing for TypeScript, React and GraphQL and will discuss our strategy implementing it, including two failed attempts. When leaving this session you will have learned which tactics to apply when modernizing a web stack and warning signs to be aware off.
System Development Life Cycle
The document discusses and compares two software development life cycle (SDLC) models: the waterfall model and evolutionary model. The waterfall model involves 5 sequential phases: requirements analysis, design, implementation, testing, and maintenance. However, it is inflexible and does not allow for updates based on user feedback. The evolutionary model involves iterative development of prototypes based on basic requirements, with customer feedback and modifications to subsequent versions. This model is better suited for developing online systems and user interfaces as it allows for evolution through use.
Building Scalable Development Environments
The document provides guidelines for building scalable development environments in 3 main areas:
1. Establish standard programming styles and coding practices to reduce bugs and improve readability. This includes using source control, peer review, and coding standards.
2. Implement a multi-tier environment with separate development, staging, and production servers to allow for testing at each stage.
3. Employ practices like unit testing, functional testing, and benchmarking to ensure quality and performance as the system grows.
Chapter 3 Software Process Model.ppt
This document provides an overview of different software process models. It discusses the build and fix model, why models are needed to address issues like schedule and cost overruns. It covers process models as a "black box" and "white box" approach. Prescriptive models advocate an orderly approach and include activities like communication, planning, modeling etc. The waterfall model is described as having sequential phases of requirements, design, implementation, testing and maintenance. Limitations are noted. Incremental process models deliver software in increments that build on each other. RAD aims for a very short development cycle through reuse. Evolutionary models produce increasingly complete versions through iterations like prototyping, the spiral model and concurrent development.
Ajax Performance
The document discusses optimizing performance for Ajax applications. It recommends:
- Keeping client-side code light by only requesting necessary data from the server via JSON messages.
- Avoiding unnecessary DOM touches and reflows which are computationally expensive.
- Measuring performance before and after optimizations to validate improvements rather than relying on intuition.
- Optimizing algorithms and avoiding unnecessary work rather than prematurely optimizing without evidence of need.
Software Process Model in software engineering
This document provides an overview of different software process models. It discusses the build and fix model, why models are needed to address issues like schedule and cost overruns. It covers process models as a "black box" and "white box" approach. Prescriptive models advocate an orderly approach and include activities like communication, planning, modeling etc. The waterfall model is described as having sequential phases of requirements, design, implementation, testing and maintenance. Limitations are noted. Incremental process models deliver software in increments. RAD aims for a very short development cycle through reuse. Evolutionary models produce increasingly complete versions through iterations, such as with prototyping, the spiral model and concurrent development.
Developers’ mDay u Banjoj Luci - Milan Popović, PHP Srbija – Testimony (about...
This document discusses the importance of testing software. It outlines 30 tips for writing tests, including writing tests before code, treating tests like code, minimizing asserts per test, using data providers, and allocating time for testing in estimates. Testing helps catch bugs, improve code quality, and ensure stability. The document emphasizes that automated testing is key and should test everything that could break an app.
Future of QA
The document discusses predictions for the future of testing and QA. It predicts that test automation will significantly increase from 31% currently to become a major part of the QA process. It also predicts that testing responsibilities will move earlier in the development cycle, with more testing by developers and end users. Requirements testing will also improve with automation and new technologies that provide 100% test coverage and automatically generate test cases.
Futureofqa
The document discusses predictions for the future of testing and QA. It predicts that test automation will significantly increase from 31% currently to become a major part of the QA process. It also predicts that testing responsibilities will move earlier in the development cycle, with more testing by developers and end users. Requirements testing will also improve with automation and new technologies that provide 100% test coverage and automatically generate test cases.
Why test with flex unit
The document discusses why software developers should use FlexUnit, an automated unit testing framework for Flex and ActionScript projects. It notes that developers spend 80% of their time debugging code and that errors found later in the development process can cost 100x more to fix than early errors. FlexUnit allows developers to automate unit tests so that tests can be run continually, finding errors sooner when they are cheaper to fix. Writing automated tests also encourages developers to write better structured, more testable and maintainable code. FlexUnit provides a testing architecture and APIs to facilitate automated unit and integration testing as well as different test runners and listeners to output test results.
Test Driven Development (TDD) with FlexUnit 4 - 360|Flex San Jose preso
This document discusses Test Driven Development (TDD) and how to implement it using FlexUnit 4 for a Twitter companion application. It provides an overview of TDD, outlines the process which includes defining objectives, writing user stories, and creating tests before code. It demonstrates how to set up the application, create a test suite and first test case class. Finally, it provides an example of implementing the first user story to retrieve tweets with a specific hashtag by writing a test to ensure the Twitter API is called correctly and events are dispatched properly.
Test Driven Development (TDD) Preso 360|Flex 2010
This document discusses Test Driven Development (TDD) using FlexUnit 4. It provides an overview of TDD and its benefits. It then walks through an example of building a Twitter client application using TDD. It demonstrates how to create test suites and test cases, write tests to fail initially, then write code to pass the tests. It covers concepts like user stories, assertions, refactoring tests. The document recommends TDD for APIs, frameworks and services, but not GUI testing. It provides resources to learn more about TDD with FlexUnit 4 and Adobe technologies.
SW Engineering Management
- Software engineering is extremely complex and expensive work, with large software systems costing more than buildings and often having high failure rates.
- The two main factors that cause "runaway" software projects that exceed budgets and schedules are poor estimation done too early and unstable requirements that change frequently.
- Programmers are often given impossible tasks with too much work and not enough time, leading them to produce workarounds and quick fixes rather than well-designed solutions.
Pm soln9416141129710
This document discusses Boehm's top 10 principles of conventional software management and important trends in improving software economics. It also covers the three generations of software development (conventional, transition, and modern practices), comparing their characteristics. Finally, it lists and explains 10 principles of conventional software engineering and the top 10 principles of modern software management.
Similar to Test Driven Development: Part 2 (20)
Agile Methodologies And Extreme Programming - Svetlin Nakov
Agile Methodologies And Extreme Programming - Svetlin Nakov
Extreme Programming Talk Wise Consulting Www.Talkwiseconsulting
Extreme Programming Talk Wise Consulting Www.Talkwiseconsulting
Extreme programming talk wise consulting - www.talkwiseconsulting
Extreme programming talk wise consulting - www.talkwiseconsulting
Developers’ mDay u Banjoj Luci - Milan Popović, PHP Srbija – Testimony (about...
Developers’ mDay u Banjoj Luci - Milan Popović, PHP Srbija – Testimony (about...
Test Driven Development (TDD) with FlexUnit 4 - 360|Flex San Jose preso
Test Driven Development (TDD) with FlexUnit 4 - 360|Flex San Jose preso
Recently uploaded
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
“I’m still / I’m still / Chaining from the Block”
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
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
20240609 QFM020 Irresponsible AI Reading List May 2024
Everything I found interesting about the irresponsible use of machine intelligence in May 2024
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Communications Mining Series - Zero to Hero - Session 1
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
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.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Video Streaming: Then, Now, and in the Future
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Recently uploaded (20)
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
20240609 QFM020 Irresponsible AI Reading List May 2024
20240609 QFM020 Irresponsible AI Reading List May 2024
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Communications Mining Series - Zero to Hero - Session 1
Communications Mining Series - Zero to Hero - Session 1
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
GraphSummit Singapore | Enhancing Changi Airport Group's Passenger Experience...
Test Driven Development: Part 2
- 1. CodeAndroid meetup Test Driven Development
- 2. Objectives Brief history of TDD Do a very basic test
- 4. “ The fundamental problem with program maintenance is that fixing a defect has a substantial (20-50 %) chance of introducing another defect.” Mythical Man Month
- 5. Today: Test Driven Development
- 9. Unable to be “explained” to the layman
- 11. Money
- 12. Energy
- 13. Traditional model: Implementation Requirements Design Verification Maintenance
- 15. Your manager/your client will have provided the specs, and you now need to “follow the process”
- 16. You are a cog in the machine.
- 17. Manufacturing & construction industries Software has requirements that are never in spec. Requirements evolve over time Software developers are rarely domain experts BDUF meant changes later on were costly Waterfall model is based on “Physical Design”
- 18. Manufacturing & construction industries BDUF meant changes later on were costly Software is difficult to change in maintenance Two teams same project.
- 24. Your manager/your client will have provided the specs, and you now need to “follow the process”
- 25. You are a cog in the machine.
- 29. Useful URLs: android-sdk/platforms/android-1.5/samples/ApiDemos My life with android (mylifewithandroid.blogspot.com) Diego Torres Milano's blog (dtmilano.blogspot.com)
- 30. “ The fundamental problem with program maintenance is that fixing a defect has a substantial (20-50 %) chance of introducing another defect.” Mythical Man Month