Writing Maintainable Test Automation
•Download as PPTX, PDF•
0 likes•36 views
This presentation was given at IBM to introduce a few basic concepts for new test automation engineers to begin to think about writing their code in a cleaner, more maintainable way.
Report
Share
Report
Share
Recommended
The Software Engineering process in Everyware Technologies
The document discusses best practices for software engineering projects with customers. It recommends (1) understanding the customer's needs through open communication, (2) providing clear estimates and budgets, (3) collaborating on design and prototypes to ensure customer satisfaction, and (4) maintaining the relationship after a project is completed through support and potential new features. The overall message is that software development requires an ongoing, collaborative process between engineers and customers.
Being successful with Agile by Rasmus Runberg and Andrew Schumer
Agile is a great word, it's short, suggests an athletic approach to something. It fills our minds with images of gleaming, slick perfect machines, almost "German" in its implementation. So its interesting that our experience is something far more complex and messy then this word will have you believe.
Being Agile takes commitment and hard work, work with processes and people, ensuring that there is focus on the goals throughout the organisation while it scales, this also means working with the clients to embrace this mentality.
You could say we aren't Agile, rather we are constantly increasing our Agility. This changes the idea from a perfect athlete in the Olympics, to an individual working, sweating and persevering.
It is hard, it is complicated! But, by sharing our stories we will tell you why it’s also fun and worth it.
Page objects: the good, the bad, the ugly
This is a talk from the Triangle Test Automation Users Group in the Raleigh-Durham, NC area. It discusses the reasons page objects are so popular and dives into common pitfalls of using them and how to avoid them.
The Anatomy of a Code Review
Code review is a very useful tool to help keeping your code quality, besides bringing other benefits to the code author and the reviewers. In this talk, I'll show in details how a code review process works, and why all code from your team should pass through this process.
Big code refactoring with agility
The document discusses strategies for handling big code refactoring within agile methodologies. It describes various refactoring approaches like "big bang", "divide and conquer", and planned refactoring periods. The best approach emphasized is incremental refactoring as a regular part of work to continuously improve code quality. Agile practices like defining a clear vision, completing work in small batches, and iterating help enable big refactoring. Tools like trunk-based development, branch by abstraction, and feature toggles can also aid refactoring within agile.
Mastering Code Reviews
Does your team do code reviews? If not why? Are you afraid or worried about something? If they do, awesome. Do you want to learn how to improve the process? This session we will dive into the art of the Code Review. We will learn how to avoid pitfalls and how to reap the rewards of this awesome
{10.0} Test Driven Development.pptx
Test driven development involves writing tests before writing code to make the tests pass. This ensures code is built to satisfy explicit requirements. The TDD process is: write a failing test, write code to pass the test, refactor code. This improves quality by preventing defects and ensuring code is maintainable through extensive automated testing. Acceptance TDD applies this process on a system level to build the right functionality.
Effective code reviews
This document discusses effective code reviews. It begins by defining what perfect and imperfect code is, and defines a defect as anything that may cause additional costs. It explains how the cost to fix defects grows exponentially the later they are found. The document advocates fixing all defects found to improve quality and profitability. It provides tips for improving review efficiency, and outlines the roles and mindsets of authors and reviewers. The goal is for authors and reviewers to work as peers to improve code quality through thorough and respectful reviews.
Recommended
The Software Engineering process in Everyware Technologies
The document discusses best practices for software engineering projects with customers. It recommends (1) understanding the customer's needs through open communication, (2) providing clear estimates and budgets, (3) collaborating on design and prototypes to ensure customer satisfaction, and (4) maintaining the relationship after a project is completed through support and potential new features. The overall message is that software development requires an ongoing, collaborative process between engineers and customers.
Being successful with Agile by Rasmus Runberg and Andrew Schumer
Agile is a great word, it's short, suggests an athletic approach to something. It fills our minds with images of gleaming, slick perfect machines, almost "German" in its implementation. So its interesting that our experience is something far more complex and messy then this word will have you believe.
Being Agile takes commitment and hard work, work with processes and people, ensuring that there is focus on the goals throughout the organisation while it scales, this also means working with the clients to embrace this mentality.
You could say we aren't Agile, rather we are constantly increasing our Agility. This changes the idea from a perfect athlete in the Olympics, to an individual working, sweating and persevering.
It is hard, it is complicated! But, by sharing our stories we will tell you why it’s also fun and worth it.
Page objects: the good, the bad, the ugly
This is a talk from the Triangle Test Automation Users Group in the Raleigh-Durham, NC area. It discusses the reasons page objects are so popular and dives into common pitfalls of using them and how to avoid them.
The Anatomy of a Code Review
Code review is a very useful tool to help keeping your code quality, besides bringing other benefits to the code author and the reviewers. In this talk, I'll show in details how a code review process works, and why all code from your team should pass through this process.
Big code refactoring with agility
The document discusses strategies for handling big code refactoring within agile methodologies. It describes various refactoring approaches like "big bang", "divide and conquer", and planned refactoring periods. The best approach emphasized is incremental refactoring as a regular part of work to continuously improve code quality. Agile practices like defining a clear vision, completing work in small batches, and iterating help enable big refactoring. Tools like trunk-based development, branch by abstraction, and feature toggles can also aid refactoring within agile.
Mastering Code Reviews
Does your team do code reviews? If not why? Are you afraid or worried about something? If they do, awesome. Do you want to learn how to improve the process? This session we will dive into the art of the Code Review. We will learn how to avoid pitfalls and how to reap the rewards of this awesome
{10.0} Test Driven Development.pptx
Test driven development involves writing tests before writing code to make the tests pass. This ensures code is built to satisfy explicit requirements. The TDD process is: write a failing test, write code to pass the test, refactor code. This improves quality by preventing defects and ensuring code is maintainable through extensive automated testing. Acceptance TDD applies this process on a system level to build the right functionality.
Effective code reviews
This document discusses effective code reviews. It begins by defining what perfect and imperfect code is, and defines a defect as anything that may cause additional costs. It explains how the cost to fix defects grows exponentially the later they are found. The document advocates fixing all defects found to improve quality and profitability. It provides tips for improving review efficiency, and outlines the roles and mindsets of authors and reviewers. The goal is for authors and reviewers to work as peers to improve code quality through thorough and respectful reviews.
Software Craftsmanship @ Ntnu
The document discusses software craftsmanship and test-driven development (TDD). It notes that software craftsmanship is about raising the bar, taking pride in work, discipline, continuous learning, and deliberate practice. TDD's goal is to write clean code that works, following the Red-Green-Refactor mantra of writing a failing test, making it pass quickly, and refactoring code. The document promotes writing clean code because it is less expensive to maintain and leads to better programmers and productivity.
Adopting Agile
These slides quickly illustrate how you can successfully adopt Agile to improve your development efforts. In addition to discussing how and why teams are interested in Agile, it covers some of the challenges of adopting it and suggestions for ensuring success.
Refactoring Big Design Smells : Presented by Sanjay Kumar
Agile design or emergent design relies heavily on timely refactoring efforts that aim to improve existing design. Yet often, when the code base grows or when someone else's code is handed over to us, there is a reluctance to refactor existing code - despite an obvious design smell. While the reasons to avoid refactoring may be well-grounded – lack of time, lack of understanding or fear of breaking it – in the long term, delaying code refactoring makes the code rot further. And, as a result, technical debt continues to pile up.
This session begins by reviewing common design smells, discusses five key features of good code and then discusses a common yet often overlooked design smell in detail – big methods. Using an example of a big method, it proposes a refactoring strategy that will ensure that a refactoring effort does not cause any negative side effects. During the session, participants are walked through a real code refactoring example – step by step.
Clean and Green Code
This presentation discusses the Clean and Green Code initiative to promote writing cleaner code. It encourages coders to rebuild their will to write beautiful, reusable code through discipline and making coding a form of recreation again. Clean code is defined as simple, well-structured, robust, efficient and passes all tests, making comments redundant. Writing clean code leads to green outcomes like tests passing with green results, high code maintainability, and lower carbon footprints from code execution and technologies used. Reasons why coders don't always write clean code are discussed. The presentation pledges that coders will take responsibility for writing clean and green code.
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
The document discusses test-driven development (TDD). TDD is a software development process where test cases are created to specify requirements before code is written to pass those tests. This ensures code meets requirements. Benefits of TDD include fewer bugs due to comprehensive testing, and ability to refactor code without breaking functionality. The document provides examples of different types of tests and outlines best practices for getting started with TDD.
The perfect PR
This document provides tips for creating effective pull requests. It recommends that submitters review their own code, write clear titles and descriptions, use good commit messages, and keep code changes short. Reviewers should provide constructive feedback, ask questions, and review in short sessions. Tools like code analysis and checklists can help reviewers. Pair programming and early feedback can improve code quality before a pull request. The goal is for teams to work collaboratively through the pull request process.
Why Is Manufacturing Difficult?
Dragon Innovation's, Dr. Anna C. Thornton, reviews the inherent challenges of manufacturing, specifically as it pertains to Hardware/Consumer Electronics products. Planning, production phases, factory selection, quality planning & testing, and much more are included in this overview. This lecture took place as part of MIT's brand new IDM program in February 2016.
Test Driven Development with Laravel
This document discusses test driven development (TDD) with Laravel. It begins with an introduction to the author and overview of TDD. The main benefits of TDD are described as code confidence, cleaner code, and fewer bugs. An example of building tests for a car wash management tool is provided to demonstrate the TDD cycle of red-green-refactor. Key points are made about what to test, including focusing on data transformations and keeping controllers skinny. Views are generally not tested, but using presenters allows views to be fully tested.
Removing-the-cost-coding-errors-in-building-materials
Consumers, business partners and regulatory
authorities demand more accurate product codes and
information. Are processes and today’s coding systems
up to meeting that challenge?
Agile & Test Driven Development: The Ampersand Commerce Approach
A presentation to University of Manchester Computer Science graduates about how Ampersand Commerce approaches Agile and Test Driven Development. Also, information about our graduate programme for software engineers
Code with Honor – on the importance and beauty of software programming - RMOU...
We want to be able to look our customer (and our mom) in the eye and state that we are proud of the software we have delivered. Because it is a high quality and lasting product. But can we really? Let’s discuss how to bring our profession to the next level.How to be a Professional Software Professional
Abstract
As programmers, our main goal is to make IT work. To translate functional specification into executable code. And sure, that is the least we can do. But we have more responsibility than this. We have to produce software that is robust and will reliably handle expected and unexpected cases. Software that is scalable and can handle expected and somewhat unexpected load gracefully. With minimal operating costs and in the greenest way possible. Software that is observable and manageable and that can be evolved with changing and new functional requirements and with changing technology. Software that will be legacy in the original, positive meaning of the word. That does not depend on the one big brain in our team or on the guy that has been around for three decades. Software that we know is good and can comfortably be modified in a controlled and productive way.
This session talks about what it takes to create our code with honor. It discusses automation at every level in the build, rollout and monitoring of infrastructure (as code), platform and application, using CI/CD pipelines and DevOps procedures and tool. The session talks about testing – before and during development as well as after each change anywhere in the system and for both functional and non-functional aspects. Test driven development, regression testing and smoke testing are among the concepts discussed. The term ‘clean code’ refers to code that is readable, testable and maintainable. Through code analysis and peer reviews and by performing refactoring we constantly refine our software to be collectively adaptable.
As software developers, we have an obligation to society, to our peers and to ourselves to not only write software that does the job, but to create code that is good. Ours is a great and meaningful line of work, especially if we raise our game professionally to code with honor.
Benefits:
* feel the responsibility we IT professionals have
* understand how and why we frequently fail in the responsibility
* learn about the key aspects to apply to find the road to redemption
To test or not to test? this is the prblem
This document discusses the debate around software testing - whether or not it is worthwhile for companies, especially startups, to implement testing practices. It acknowledges both benefits of testing like improved quality and reduced bugs, as well as challenges like increased time and costs. The document provides examples of how to effectively sell the value of testing to customers and overcome objections. It emphasizes that testing leads to more maintainable code and helps avoid technical debt.
Test Driven Development by Sameer Arora
Test-driven development (TDD) is a software development process where test cases are developed before code to validate requirements. The TDD process involves repeatedly writing a test, making it fail, then writing code to pass the test and refactoring code. TDD results in code with fewer defects, quicker feedback, and requirements that drive design. Tests cover valid and invalid inputs, errors, boundaries, and everything that could break. TDD improves development cycles, defects, documentation, and competitive advantage for businesses.
Going Independent - making it as a freelance web professional
The document provides guidance for developers considering going independent as solo practitioners. It discusses setting up as an independent contractor, including choosing an organizational structure like an LLC, addressing legal and financial issues, and using contracts. It also offers tips for finding work through networking, job boards, and making oneself discoverable online with a website, portfolio, and social media presence. The document concludes with guidance on getting paid, including setting competitive rates, using invoicing, and collecting payments.
Test Driven Development and Automation
This document discusses test driven development (TDD) and automation for PHP projects. It covers what TDD is, why it should be done, where tests should run, who should adopt TDD, and why unit testing, code coverage, code sniffing and Selenium are important. It also discusses tools for PHP TDD like Xdebug, PHPUnit, PHP_CodeSniffer and IDEs. The document provides examples of writing test cases with the red-green-refactor process and integrating TDD into a build system with automated testing on every code change.
How to successfully grow a code review culture
As a team grows, code ownership is distributed. Code review becomes increasingly important to support the maintainability of complex codebases. An effective code base is on that can be worked on collaboratively by a team.
In this talk we'll discuss how to introduce a successful code review culture to your development team that will foster the idea of shared ownership. This in turn will result in a happy and healthy code base.
https://webexpo.net/prague2016/talk/how-to-successfully-grow-a-code-review-culture/
Custom built software and blts are not the same
Equal Experts is a network of experienced software consultants specializing in agile delivery of custom-built software solutions for businesses. The document discusses principles for determining when to build versus buy software components, noting that organizations should build what differentiates them and buy what does not. Custom software allows realizing value sooner by only building what is truly valuable and limiting development only by imagination.
Shift Up
The document discusses the need for organizations to shift testing practices to keep up with changes in technology, customers, and business models. It advocates for a "Shift-Up" approach where testing is continuous, leverages AI and automation, and accounts for a variety of customer types and scenarios. This Shift-Up helps complete the DevOps circuit by enabling earlier testing, better coverage across technologies, and continuous monitoring to surpass customer expectations.
Agile testingandautomation
1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important.
2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews.
3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.
You cant be agile if your code sucks
What is "Agile"?
Why would someone like to be agile?
What are the 3 pillars for agile software development?
How can you achieve technical excellence in your software teams?
Are developer skills more important than languages, methods or frameworks?
Executable Specifications with FitNesse and Selenium
Dawn Cannan is a QA manager who has been in software testing for 10 years. She will discuss executable specifications using FitNesse and Selenium. She will demonstrate how to create automated tests using these tools and the test automation pyramid. She will also reference her blog and links to learn more about FitNesse, Selenium, and her Selenesse open source project.
Executable Specifications with FitNesse and Selenium
This document discusses using executable specifications with FitNesse and Selenium to minimize miscommunications between business and development teams. It introduces Dawn Cannan and describes the Test Automation Pyramid. Key points covered include defining examples as tests to get everyone on the same page early, preventing bugs, and challenges of test automation in the browser like locating elements and synchronization. The FitNesse framework is presented as a way to define Selenium tests in a wiki accessible to all team members.
More Related Content
Similar to Writing Maintainable Test Automation
Software Craftsmanship @ Ntnu
The document discusses software craftsmanship and test-driven development (TDD). It notes that software craftsmanship is about raising the bar, taking pride in work, discipline, continuous learning, and deliberate practice. TDD's goal is to write clean code that works, following the Red-Green-Refactor mantra of writing a failing test, making it pass quickly, and refactoring code. The document promotes writing clean code because it is less expensive to maintain and leads to better programmers and productivity.
Adopting Agile
These slides quickly illustrate how you can successfully adopt Agile to improve your development efforts. In addition to discussing how and why teams are interested in Agile, it covers some of the challenges of adopting it and suggestions for ensuring success.
Refactoring Big Design Smells : Presented by Sanjay Kumar
Agile design or emergent design relies heavily on timely refactoring efforts that aim to improve existing design. Yet often, when the code base grows or when someone else's code is handed over to us, there is a reluctance to refactor existing code - despite an obvious design smell. While the reasons to avoid refactoring may be well-grounded – lack of time, lack of understanding or fear of breaking it – in the long term, delaying code refactoring makes the code rot further. And, as a result, technical debt continues to pile up.
This session begins by reviewing common design smells, discusses five key features of good code and then discusses a common yet often overlooked design smell in detail – big methods. Using an example of a big method, it proposes a refactoring strategy that will ensure that a refactoring effort does not cause any negative side effects. During the session, participants are walked through a real code refactoring example – step by step.
Clean and Green Code
This presentation discusses the Clean and Green Code initiative to promote writing cleaner code. It encourages coders to rebuild their will to write beautiful, reusable code through discipline and making coding a form of recreation again. Clean code is defined as simple, well-structured, robust, efficient and passes all tests, making comments redundant. Writing clean code leads to green outcomes like tests passing with green results, high code maintainability, and lower carbon footprints from code execution and technologies used. Reasons why coders don't always write clean code are discussed. The presentation pledges that coders will take responsibility for writing clean and green code.
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
The document discusses test-driven development (TDD). TDD is a software development process where test cases are created to specify requirements before code is written to pass those tests. This ensures code meets requirements. Benefits of TDD include fewer bugs due to comprehensive testing, and ability to refactor code without breaking functionality. The document provides examples of different types of tests and outlines best practices for getting started with TDD.
The perfect PR
This document provides tips for creating effective pull requests. It recommends that submitters review their own code, write clear titles and descriptions, use good commit messages, and keep code changes short. Reviewers should provide constructive feedback, ask questions, and review in short sessions. Tools like code analysis and checklists can help reviewers. Pair programming and early feedback can improve code quality before a pull request. The goal is for teams to work collaboratively through the pull request process.
Why Is Manufacturing Difficult?
Dragon Innovation's, Dr. Anna C. Thornton, reviews the inherent challenges of manufacturing, specifically as it pertains to Hardware/Consumer Electronics products. Planning, production phases, factory selection, quality planning & testing, and much more are included in this overview. This lecture took place as part of MIT's brand new IDM program in February 2016.
Test Driven Development with Laravel
This document discusses test driven development (TDD) with Laravel. It begins with an introduction to the author and overview of TDD. The main benefits of TDD are described as code confidence, cleaner code, and fewer bugs. An example of building tests for a car wash management tool is provided to demonstrate the TDD cycle of red-green-refactor. Key points are made about what to test, including focusing on data transformations and keeping controllers skinny. Views are generally not tested, but using presenters allows views to be fully tested.
Removing-the-cost-coding-errors-in-building-materials
Consumers, business partners and regulatory
authorities demand more accurate product codes and
information. Are processes and today’s coding systems
up to meeting that challenge?
Agile & Test Driven Development: The Ampersand Commerce Approach
A presentation to University of Manchester Computer Science graduates about how Ampersand Commerce approaches Agile and Test Driven Development. Also, information about our graduate programme for software engineers
Code with Honor – on the importance and beauty of software programming - RMOU...
We want to be able to look our customer (and our mom) in the eye and state that we are proud of the software we have delivered. Because it is a high quality and lasting product. But can we really? Let’s discuss how to bring our profession to the next level.How to be a Professional Software Professional
Abstract
As programmers, our main goal is to make IT work. To translate functional specification into executable code. And sure, that is the least we can do. But we have more responsibility than this. We have to produce software that is robust and will reliably handle expected and unexpected cases. Software that is scalable and can handle expected and somewhat unexpected load gracefully. With minimal operating costs and in the greenest way possible. Software that is observable and manageable and that can be evolved with changing and new functional requirements and with changing technology. Software that will be legacy in the original, positive meaning of the word. That does not depend on the one big brain in our team or on the guy that has been around for three decades. Software that we know is good and can comfortably be modified in a controlled and productive way.
This session talks about what it takes to create our code with honor. It discusses automation at every level in the build, rollout and monitoring of infrastructure (as code), platform and application, using CI/CD pipelines and DevOps procedures and tool. The session talks about testing – before and during development as well as after each change anywhere in the system and for both functional and non-functional aspects. Test driven development, regression testing and smoke testing are among the concepts discussed. The term ‘clean code’ refers to code that is readable, testable and maintainable. Through code analysis and peer reviews and by performing refactoring we constantly refine our software to be collectively adaptable.
As software developers, we have an obligation to society, to our peers and to ourselves to not only write software that does the job, but to create code that is good. Ours is a great and meaningful line of work, especially if we raise our game professionally to code with honor.
Benefits:
* feel the responsibility we IT professionals have
* understand how and why we frequently fail in the responsibility
* learn about the key aspects to apply to find the road to redemption
To test or not to test? this is the prblem
This document discusses the debate around software testing - whether or not it is worthwhile for companies, especially startups, to implement testing practices. It acknowledges both benefits of testing like improved quality and reduced bugs, as well as challenges like increased time and costs. The document provides examples of how to effectively sell the value of testing to customers and overcome objections. It emphasizes that testing leads to more maintainable code and helps avoid technical debt.
Test Driven Development by Sameer Arora
Test-driven development (TDD) is a software development process where test cases are developed before code to validate requirements. The TDD process involves repeatedly writing a test, making it fail, then writing code to pass the test and refactoring code. TDD results in code with fewer defects, quicker feedback, and requirements that drive design. Tests cover valid and invalid inputs, errors, boundaries, and everything that could break. TDD improves development cycles, defects, documentation, and competitive advantage for businesses.
Going Independent - making it as a freelance web professional
The document provides guidance for developers considering going independent as solo practitioners. It discusses setting up as an independent contractor, including choosing an organizational structure like an LLC, addressing legal and financial issues, and using contracts. It also offers tips for finding work through networking, job boards, and making oneself discoverable online with a website, portfolio, and social media presence. The document concludes with guidance on getting paid, including setting competitive rates, using invoicing, and collecting payments.
Test Driven Development and Automation
This document discusses test driven development (TDD) and automation for PHP projects. It covers what TDD is, why it should be done, where tests should run, who should adopt TDD, and why unit testing, code coverage, code sniffing and Selenium are important. It also discusses tools for PHP TDD like Xdebug, PHPUnit, PHP_CodeSniffer and IDEs. The document provides examples of writing test cases with the red-green-refactor process and integrating TDD into a build system with automated testing on every code change.
How to successfully grow a code review culture
As a team grows, code ownership is distributed. Code review becomes increasingly important to support the maintainability of complex codebases. An effective code base is on that can be worked on collaboratively by a team.
In this talk we'll discuss how to introduce a successful code review culture to your development team that will foster the idea of shared ownership. This in turn will result in a happy and healthy code base.
https://webexpo.net/prague2016/talk/how-to-successfully-grow-a-code-review-culture/
Custom built software and blts are not the same
Equal Experts is a network of experienced software consultants specializing in agile delivery of custom-built software solutions for businesses. The document discusses principles for determining when to build versus buy software components, noting that organizations should build what differentiates them and buy what does not. Custom software allows realizing value sooner by only building what is truly valuable and limiting development only by imagination.
Shift Up
The document discusses the need for organizations to shift testing practices to keep up with changes in technology, customers, and business models. It advocates for a "Shift-Up" approach where testing is continuous, leverages AI and automation, and accounts for a variety of customer types and scenarios. This Shift-Up helps complete the DevOps circuit by enabling earlier testing, better coverage across technologies, and continuous monitoring to surpass customer expectations.
Agile testingandautomation
1. The document discusses lessons learned about agile testing and automation. It emphasizes that testing is more than just checking and that both automated and exploratory testing are important.
2. It recommends automating output checking where possible but also using exploratory testing. It also stresses the importance of unit, integration and end-to-end tests as well as code reviews.
3. The document advocates for test-driven development and notes how automated tests can reduce regression testing time. It emphasizes that successful testing requires collaboration between developers, testers and business stakeholders.
You cant be agile if your code sucks
What is "Agile"?
Why would someone like to be agile?
What are the 3 pillars for agile software development?
How can you achieve technical excellence in your software teams?
Are developer skills more important than languages, methods or frameworks?
Similar to Writing Maintainable Test Automation (20)
Refactoring Big Design Smells : Presented by Sanjay Kumar
Refactoring Big Design Smells : Presented by Sanjay Kumar
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
Joe Cisar - Everything I Know About TDD - Agile Midwest 2019
Removing-the-cost-coding-errors-in-building-materials
Removing-the-cost-coding-errors-in-building-materials
Agile & Test Driven Development: The Ampersand Commerce Approach
Agile & Test Driven Development: The Ampersand Commerce Approach
Code with Honor – on the importance and beauty of software programming - RMOU...
Code with Honor – on the importance and beauty of software programming - RMOU...
Going Independent - making it as a freelance web professional
Going Independent - making it as a freelance web professional
More from Dawn Code
Executable Specifications with FitNesse and Selenium
Dawn Cannan is a QA manager who has been in software testing for 10 years. She will discuss executable specifications using FitNesse and Selenium. She will demonstrate how to create automated tests using these tools and the test automation pyramid. She will also reference her blog and links to learn more about FitNesse, Selenium, and her Selenesse open source project.
Executable Specifications with FitNesse and Selenium
This document discusses using executable specifications with FitNesse and Selenium to minimize miscommunications between business and development teams. It introduces Dawn Cannan and describes the Test Automation Pyramid. Key points covered include defining examples as tests to get everyone on the same page early, preventing bugs, and challenges of test automation in the browser like locating elements and synchronization. The FitNesse framework is presented as a way to define Selenium tests in a wiki accessible to all team members.
A Sampling of Tools
This document provides an overview of common tools used for test automation, including frameworks, runners, drivers, reporting tools and build systems. It discusses factors to consider like the technology stack, skills of those writing and running tests, and how test results will be viewed. Popular automation stacks like HP QTP, FitNesse, Eclipse/JUnit/Selenium/Hudson and Cucumber are described. UI drivers like Selenium, Watir and desktop testing tools are also covered. Common challenges around test design, organization and synchronization are discussed along with approaches to address them.
Testing in the Wild
This document discusses strategies for handling non-ideal testing situations when adopting agile practices. It addresses problems like lack of test automation, test data issues, legacy reporting needs, geographic distribution of teams, and separation of testers and programmers. The proposed solutions generally involve starting small, using technology to facilitate remote collaboration, targeting important information in reports, and developing relationships between team members.
Fitting Organizational Structure
This document discusses how to fit organizational structure into an agile team when the team is not fully cohesive. It addresses common issues like separate testing teams, lack of collaboration, and remote or offshore team members. The document provides suggestions for improving communication and collaboration even when organizational barriers exist, such as walking over to other teammates' desks, communicating through documentation, and discussing testing needs early in development. The overall message is that teams can still benefit from agile practices even if the organizational structure is not perfectly aligned.
Pair development
This document discusses how pairing programmers and testers during development benefits both roles. Pairing helps minimize customer feedback time, prevents defects, defines what "done" means for a task, prevents confusion, and expands the benefits of test-driven development throughout the development cycle. The document was presented by Dawn Cannan and Shannon Prue at the Agile Development Practices West 2011 conference on pairing roles and customer-driven development.
Remote Dev/Test Pairing
This document summarizes a presentation about remote pairing of developers and testers using distributed tools. It discusses how pairing helps build shared understanding and teaches skills in both directions. An example setup uses Mikogo, Skype, webcam and headset to enable remote pairing at low cost. The presentation demonstrates a wiki framework for Cucumber acceptance tests, built with Ruby on Rails and Cucumber. Remote pairing works well after an initial adjustment period.
Crowdsource Your Career
The document provides tips for crowdsourcing one's career and standing out, including using social media to share opinions and struggles, developing a network by interacting with others in one's field, and avoiding pitfalls like not sharing ideas or keeping personal social media public.
How Low Can Your Tests Go
TISQA 2018 conference, discussing strategies for determining which level of test automation that tests should go.
Exploratory testing part 2
This talk has been given a few times to internal teams, in order to introduce them to the concept of exploratory testing.
Exploratory testing part 1
This talk has been given a few times to internal teams, in order to introduce them to the concept of exploratory testing.
Exploratory testing part 3
This document discusses various techniques for exploratory testing, including thinking outside the box when testing. It provides examples of riddles and clues to stimulate new perspectives, and suggests pretending to take on different user roles to test from various viewpoints. The document also outlines heuristics like HICCUPS and considerations for testing various elements of a product like structure, function, and interfaces. It concludes with an exploratory testing dice roll technique to help guide exploratory sessions.
Agile and Exploratory Testing Jeopardy
This fun presentation is a Jeopardy! game, with concepts from Agile basics and Exploratory Testing. It can be done as Jeopardy can be- in any order, depending on the answers the audience members choose.
Pair Development from the Trenches
Inspired by "Scrum and XP from the Trenches", by Henrik Kniberg, this talk was given at the TriAgile conference in 2016, and describes in detail how developers and testers can work together more closely.
Testing Legacy Apps
The document discusses testing challenges for teams transitioning to agile and provides recommendations for addressing them. It recommends starting with automating frequent, time-consuming tasks to "stop the bleeding". It also suggests beginning pair testing and programming to facilitate collaboration between testers and developers. The document advocates filling in test automation over time using the test automation pyramid and testing quadrants frameworks as guides.
More from Dawn Code (16)
Executable Specifications with FitNesse and Selenium
Executable Specifications with FitNesse and Selenium
Executable Specifications with FitNesse and Selenium
Executable Specifications with FitNesse and Selenium
Recently uploaded
Artificia Intellicence and XPath Extension Functions
The purpose of this presentation is to provide an overview of how you can use AI from XSLT, XQuery, Schematron, or XML Refactoring operations, the potential benefits of using AI, and some of the challenges we face.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
E-commerce Application Development Company.pdf
Your business can reach new heights with our assistance as we design solutions that are specifically appropriate for your goals and vision. Our eCommerce application solutions can digitally coordinate all retail operations processes to meet the demands of the marketplace while maintaining business continuity.
LORRAINE ANDREI_LEQUIGAN_HOW TO USE ZOOM
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
OpenMetadata Community Meeting - 5th June 2024
The OpenMetadata Community Meeting was held on June 5th, 2024. In this meeting, we discussed about the data quality capabilities that are integrated with the Incident Manager, providing a complete solution to handle your data observability needs. Watch the end-to-end demo of the data quality features.
* How to run your own data quality framework
* What is the performance impact of running data quality frameworks
* How to run the test cases in your own ETL pipelines
* How the Incident Manager is integrated
* Get notified with alerts when test cases fail
Watch the meeting recording here - https://www.youtube.com/watch?v=UbNOje0kf6E
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
How to write a program in any programming language
How to write a program in any programming language
GraphSummit Paris - The art of the possible with Graph Technology
Sudhir Hasbe, Chief Product Officer, 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.
socradar-q1-2024-aviation-industry-report.pdf
SOCRadar's Aviation Industry Q1 Incident Report is out now!
The aviation industry has always been a prime target for cybercriminals due to its critical infrastructure and high stakes. In the first quarter of 2024, the sector faced an alarming surge in cybersecurity threats, revealing its vulnerabilities and the relentless sophistication of cyber attackers.
SOCRadar’s Aviation Industry, Quarterly Incident Report, provides an in-depth analysis of these threats, detected and examined through our extensive monitoring of hacker forums, Telegram channels, and dark web platforms.
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
openEuler Case Study - The Journey to Supply Chain Security
openEuler Case Study - The Journey to Supply Chain Security
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
The UI5 tooling is the development and build tooling of UI5. It is built in a modular and extensible way so that it can be easily extended by your needs. This session will showcase various tooling extensions which can boost your development experience by far so that you can really work offline, transpile your code in your project to use even newer versions of EcmaScript (than 2022 which is supported right now by the UI5 tooling), consume any npm package of your choice in your project, using different kind of proxies, and even stitching UI5 projects during development together to mimic your target environment.
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
No one wants their application to drag like a car stuck in the slow lane! Yet it’s all too common to encounter bumpy, pothole-filled solutions that slow the speed of any application. Symfony apps are not an exception.
In this talk, I will take you for a spin around the performance racetrack. We’ll explore common pitfalls - those hidden potholes on your application that can cause unexpected slowdowns. Learn how to spot these performance bumps early, and more importantly, how to navigate around them to keep your application running at top speed.
We will focus in particular on tuning your engine at the application level, making the right adjustments to ensure that your system responds like a well-oiled, high-performance race car.
Vitthal Shirke Java Microservices Resume.pdf
Software Engineering, Software Consulting, Tech Lead, Spring Boot, Spring Cloud, Spring Core, Spring JDBC, Spring Transaction, Spring MVC, OpenShift Cloud Platform, Kafka, REST, SOAP, LLD & HLD.
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS Security Version 1.2 was adopted in 2024. This revision strengthens support for long runnings systems adding new cryptographic algorithms, certificate revocation, and hardness against DoS attacks.
Hand Rolled Applicative User Validation Code Kata
Could you use a simple piece of Scala validation code (granted, a very simplistic one too!) that you can rewrite, now and again, to refresh your basic understanding of Applicative operators <*>, <*, *>?
The goal is not to write perfect code showcasing validation, but rather, to provide a small, rough-and ready exercise to reinforce your muscle-memory.
Despite its grandiose-sounding title, this deck consists of just three slides showing the Scala 3 code to be rewritten whenever the details of the operators begin to fade away.
The code is my rough and ready translation of a Haskell user-validation program found in a book called Finding Success (and Failure) in Haskell - Fall in love with applicative functors.
Webinar On-Demand: Using Flutter for Embedded
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Graspan: A Big Data System for Big Code Analysis
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
What is Augmented Reality Image Tracking
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Presentation from Ghazal Aakel and Eric Jochum at the GSD Community Stage Meetup on June 6th, 2024
Recently uploaded (20)
Artificia Intellicence and XPath Extension Functions
Artificia Intellicence and XPath Extension Functions
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Neo4j - Product Vision and Knowledge Graphs - GraphSummit Paris
Fundamentals of Programming and Language Processors
Fundamentals of Programming and Language Processors
How to write a program in any programming language
How to write a program in any programming language
GraphSummit Paris - The art of the possible with Graph Technology
GraphSummit Paris - The art of the possible with Graph Technology
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
openEuler Case Study - The Journey to Supply Chain Security
openEuler Case Study - The Journey to Supply Chain Security
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
UI5con 2024 - Boost Your Development Experience with UI5 Tooling Extensions
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
DDS-Security 1.2 - What's New? Stronger security for long-running systems
DDS-Security 1.2 - What's New? Stronger security for long-running systems
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
ALGIT - Assembly Line for Green IT - Numbers, Data, Facts
Writing Maintainable Test Automation
- 1. WRITING MAINTAINABLE TEST AUTOMATION AVOIDING COMMON AUTOMATION PITFALLS
- 2. IS TEST AUTOMATION CODE REAL CODE? SHOULD AUTOMATION CODE BE WRITTEN FOLLOWING THE SAME CONVENTIONS AS PRODUCTION DEVELOPERS WRITING PRODUCTION CODE?
- 4. DOES THAT MEAN WE SHOULD IGNORE ALL CLEAN CODING PRACTICES? OF COURSE NOT
- 5. WHY SHOULD WE BOTHER?
- 6. BUT REFACTORING HAS A COST, TOO
- 7. THE HAPPY MEDIUM • NO NEED TO GET INTO DEEP, TECHNICAL, PROGRAMMING CONCEPTS • ALSO WE DO NOT WANT TO END UP WITH A PROJECT THAT COSTS MORE TO MAINTAIN THAN IT IS WORTH TO EXECUTE • TESTERS CAN START WITH SOME SMALL PRACTICES THAT WORK TOWARD CLEAN, MAINTAINABLE, CODE
- 8. MAKE CODE HUMAN READABLE • CODE IS READ BY HUMANS, NOT COMPUTERS • CODE SHOULD CONVEY INTENT • NAMES SHOULD BE MEANINGFUL • NAMES SHOULD NOT BE ABBREVIATED
- 10. HOW COULD WE MODIFY THIS?
- 11. MAYBE LIKE THIS?
- 12. DRY: DON’T REPEAT YOURSELF • IF YOU FIND THAT YOU DO IT MORE THAN ONCE, PULL IT OUT INTO A SEPARATE METHOD • IF YOU FIND THAT YOU ARE COPYING AND PASTING CODE, CONSIDER WHETHER YOU ARE REPEATING YOURSELF
- 13. WHAT HAPPENS THE NEXT TIME WE WANT TO OPEN THAT EXCEL SPREADSHEET?
- 15. WHAT ABOUT WHEN ANOTHER USER NEEDS TO PUT THEIR OWN PATH IN?
- 17. WHAT ABOUT WHEN WE NEED TO INSERT A SHEET AS SHEET 1 IN THESE EXCEL FILES?
- 19. EVEN BETTER …
- 20. LET’S START THERE • NAME ALL VALUES WITH MEANINGFUL, RELEVANT, HUMAN-READABLE NAMES • DON’T REPEAT YOURSELF
- 21. FOR FURTHER READING • WRITING MAINTAINABLE AUTOMATED TESTS, BY DALE EMERY
- 22. FOR EVEN FURTHER READING