What if designers approached collaboration and critique more like developers? Could it make us better designers, and could it better collaboration between designers and developers? Presented at Yggdrasil 2018 in Sandefjord, Norway
When you work in a small collocated team many engineering practices and approaches are relatively easy to use and adapt. In large project with many teams working on the same product this task is not so simple. I want to share experience report in implementing Code Review practice in big product development team (more than 150 people, 10+ feature teams). In this talk we will review what approaches works in such setup and what don’t work, what tools and additional practices are needed to support Code Review and make it more effective, what difficulties and blockers will you probably see in the real life cases, what useful metrics could be produced by this practice.
Gamification in outsourcing company: experience report.Mikalai Alimenkou
Most of us used to hear word gamification only for end user engagement into product usage. Some of us know about usage of similar approaches in product development teams to improve and tune development process. But almost nobody believes that gamification is possible in the context of outsourcing companies and teams. This talk is experience report of gamification usage on very large project with detailed reusable framework demonstration. If you want to bring some fun and really engage your team, then this talk is for you.
With Agile adoption many things have changed in quality assurance and tester role. Ourdays the whole team is responsible for product quality. But not so many people understand how such high level approaches work in practice, how developer interacts with tester, what stages each task passes on the way from requirements specification to customer acceptance, who is doing what at each stage.
I have met only few teams, where developer and tester work closely together on a daily basis. Some projects try to same money on developer's time, others try to have independent testing team without influence from developers side. Developers also don't understad how tester could help them in practice. But this pair is able to significantly improve product quality and avoid many common issues.
In this talk we will cover motivation behind pair work of develoeper and tester, concrete practices and approaches at different stages, and advantages that both sides could achieve from such work style.
The document discusses the role and mindset of a quality assurance (QA) engineer. It states that while developers aim to be optimists about code outcomes, QA engineers must be natural pessimists and question what could go wrong. QA engineers need to execute test scenarios to check requirements and boundary conditions are met. They should be curious and explore areas beyond normal tests. Key responsibilities of QA engineers include reviewing test cases from various sources, performing integration and exploratory testing, and incorporating different test types throughout the software development process.
Software testers and QA Engineers play a vital role in any firm. And with time and practice, they will be able to aim for higher positions and pay cheques. Here are the pros and cons of choosing Software testing as a career path.
This document provides an overview of agile testing and different types of tests used in agile development. It discusses testing in an agile context to respond to change through continuous testing with fast feedback. Various types of tests are described, including functional, unit, integration, and usability tests. Unit testing is explored in more detail, covering concepts like test structure, isolation, and characteristics of good unit tests. The document also distinguishes between unit testing and test-driven development (TDD), showing TDD follows unit testing in a particular order.
The document discusses how the role of testers has evolved over time as business and technology changes accelerated. It describes how testing jobs now require strong programming skills. It also presents a model that positions testing as a team activity that provides empirical evidence across many dimensions to support product quality. The document advocates for testers to think analytically, be curious and critical, and apply their skills broadly to contribute in various roles on a team.
When you work in a small collocated team many engineering practices and approaches are relatively easy to use and adapt. In large project with many teams working on the same product this task is not so simple. I want to share experience report in implementing Code Review practice in big product development team (more than 150 people, 10+ feature teams). In this talk we will review what approaches works in such setup and what don’t work, what tools and additional practices are needed to support Code Review and make it more effective, what difficulties and blockers will you probably see in the real life cases, what useful metrics could be produced by this practice.
Gamification in outsourcing company: experience report.Mikalai Alimenkou
Most of us used to hear word gamification only for end user engagement into product usage. Some of us know about usage of similar approaches in product development teams to improve and tune development process. But almost nobody believes that gamification is possible in the context of outsourcing companies and teams. This talk is experience report of gamification usage on very large project with detailed reusable framework demonstration. If you want to bring some fun and really engage your team, then this talk is for you.
With Agile adoption many things have changed in quality assurance and tester role. Ourdays the whole team is responsible for product quality. But not so many people understand how such high level approaches work in practice, how developer interacts with tester, what stages each task passes on the way from requirements specification to customer acceptance, who is doing what at each stage.
I have met only few teams, where developer and tester work closely together on a daily basis. Some projects try to same money on developer's time, others try to have independent testing team without influence from developers side. Developers also don't understad how tester could help them in practice. But this pair is able to significantly improve product quality and avoid many common issues.
In this talk we will cover motivation behind pair work of develoeper and tester, concrete practices and approaches at different stages, and advantages that both sides could achieve from such work style.
The document discusses the role and mindset of a quality assurance (QA) engineer. It states that while developers aim to be optimists about code outcomes, QA engineers must be natural pessimists and question what could go wrong. QA engineers need to execute test scenarios to check requirements and boundary conditions are met. They should be curious and explore areas beyond normal tests. Key responsibilities of QA engineers include reviewing test cases from various sources, performing integration and exploratory testing, and incorporating different test types throughout the software development process.
Software testers and QA Engineers play a vital role in any firm. And with time and practice, they will be able to aim for higher positions and pay cheques. Here are the pros and cons of choosing Software testing as a career path.
This document provides an overview of agile testing and different types of tests used in agile development. It discusses testing in an agile context to respond to change through continuous testing with fast feedback. Various types of tests are described, including functional, unit, integration, and usability tests. Unit testing is explored in more detail, covering concepts like test structure, isolation, and characteristics of good unit tests. The document also distinguishes between unit testing and test-driven development (TDD), showing TDD follows unit testing in a particular order.
The document discusses how the role of testers has evolved over time as business and technology changes accelerated. It describes how testing jobs now require strong programming skills. It also presents a model that positions testing as a team activity that provides empirical evidence across many dimensions to support product quality. The document advocates for testers to think analytically, be curious and critical, and apply their skills broadly to contribute in various roles on a team.
The document discusses automation testing and unit testing with JUnit. It defines automation testing as using a software to test a product by writing scripts to rerun test scenarios quickly. Unit testing tests individual software units in isolation to check for correct behavior. The document also describes Selenium as a tool for automating web application testing and JUnit as the most popular unit testing framework for Java. It notes the benefits of both automation and unit testing as reducing costs and bugs while improving quality.
Looking to move to Continuous Delivery? Worried about the quality of your the code? Helping your developers understand clean-code practices and getting the right testing strategy in place can take a while. What should you do to control the quality of the incoming code till then? This talk shares our experience of using PRRiskAdvisor to gradually educate and influence developers to write better code and also help the code reviewer to be more effective at their reviews.
Every time a developer raises a pull-request, PRRiskAdvisor analyzes the files that were changed and publishes a report on the pull request itself with the overall risk associated with this pull request and also risk associated with each file. It also runs static code analysis using SonarQube and publishes the configured violations as comments on the pull request. This way the reviewer just has to look at the pull request to get a decent idea of what it means to review this pull request. If there are too many violations, then PRRiskAdvisor can also automatically reject the pull request.
By doing this, we saw our developers starting paying more attention to clean code practices and hence the overall quality of the incoming code improved, while we worked on putting the right engineering practices and testing strategy in place.
More details: https://confengine.com/last-conference-canberra-2018/proposal/7294/improving-the-quality-of-incoming-code
Conference Link: https://2019.agileindia.org
Almost any application or software system manages data. It is hard to imagine test automation that is not affected by this fact. There are many differenct approaches how to prepare system under test, providing predefined test data: use application UI, invoke API methods, run business logic directly, access DB from test scenarios, etc. In this talk we will review most of existing approaches, starting from the easiest and the most popular ones and finishing with really tricky ways to manage your test data for large distributed systems. There is no ideal solution for every case or silver bullet, but I hope your toolset will become wider after visiting this talk.
This document discusses test driven development (TDD) for testers. It provides an overview of TDD, including writing tests before code, different types of tests, and the testing roles of developers versus testers. Developers are said to be "solution space" people who write unit and integration tests to drive code design, while testers are "problem space" people who focus on exploring potential problems and edge cases without limitations. Both developers and testers should work to avoid redundant testing and place the right types of tests in the right locations.
This document summarizes a concise QA and testing process developed for a small startup. It includes protocols for building, testing, managing changes, and releasing software. The build protocol ensures testing receives builds and information about changes. The test cycle protocol defines different types of testing cycles. The change protocol establishes feature freezes and code freezes to control changes late in development. The release protocol details the release approval and packaging process.
Pertanyaan dan jawaban (graham et.al 2011) part 3ikhwana luthfi
This document contains 5 multiple choice questions about software testing from a source titled "Graham et.al (2011)" along with the answers in Indonesian.
The questions cover topics like:
- Triggers for maintenance testing
- What testers should be doing when design documents are available
- The most effective testing technique for improving code maintainability
- Who is responsible for documenting issues in a formal review
- What type of issue is best found through static analysis
YouTube Link: https://youtu.be/cv6GvRCIuTs
** Test Automation Masters Program: https://www.edureka.co/masters-progra... **
This Edureka PPT on "What is Software Testing?" will give you a brief introduction to what software testing and all the basics concept related to software testing.
The following are the topics covered in the session:
Software Risks
What is Software Testing?
Principles of Sofware Testing
Software Testing Life Cycle
Dynamic Software Testing
Future of Sofware Testing
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Why Automated Testing Matters To DevOpsdpaulmerrill
“Automated testing is a pain in my ear! Why can’t QA get it right? Why do the tests keep breaking? And for Pete’s sake, stop blaming the infrastructure!”
…Ok, maybe you chose a different word than “ear”.
How often do you have thoughts like this? Daily?
Let’s talk about these frustrations, why they exist and how we can use them to improve our systems!
In this talk, Paul Merrill, founder and Principal Automation Engineer at Beaufort Fairmont explores why automated testing matters to DevOps. Join us to learn how automated testing can be a useful tool in the creation and release of your systems!
Working in many companies as consultant, delivery manager or tech lead I have always seen the same mistakes made in test automation process. I could count successful cases on fingers of one hand. Sometimes people don’t understand the true value of test automation, sometimes just could not organize this process spending lots of money and time without any significant result. I want to share 5 top mistakes aggregated from whole my practice and solutions I recommend for them.
What is the difference between manual testing and automation testingEr Mahednra Chauhan
Manual testing involves human testers executing test cases, while automation testing uses automation tools to run test cases. Manual testing is time-consuming and relies on human resources, whereas automated testing is significantly faster. While manual testing requires investment in human resources, automation testing requires investment in testing tools and automation engineers who have programming knowledge.
Coding and testing in Software EngineeringAbhay Vijay
The document discusses various aspects of software engineering coding practices. It describes the coding phase where design is transformed into code and tested. It emphasizes the importance of coding standards and guidelines to ensure uniform and understandable code. It also discusses code review, documentation, testing approaches like black box and white box testing, and the objectives of testing.
How will you benefit from auditing your code?
We prepared a summary of the most important advantages of performing a code audit.
Curious how to do it correctly? Click the link https://bit.ly/how-to-audit-your-code-li to check out a step by step guide, a checklist, and a sample report from an audit!
Basic of Software Testing. This presentation give course overview hosted on nimble e-learning platform.Presentation is just to give you brief overview of software testing.
The document discusses various topics related to technical interview questions for software testing. It covers software testing basics like the PDCA cycle and different testing types (white box, black box, gray box). It also discusses usability testing, defect categories, defining a testing policy, preparing acceptance plans, configuration management, code coverage tools, and different testing models. Key software development phases like design, coding, and their relative defect rates are examined. The roles of different testing teams and how test documents span the SDLC are outlined. Common testing concepts like test cases, logs, traceability, entry/exit criteria, verification vs validation are defined.
Testing and DevOps Culture: Lessons LearnedLB Denker
This document discusses the speaker's background and experiences with software engineering practices. It covers his education in computational mathematics and computer science, past roles at Universal Instruments developing machine software and at Google and Etsy implementing DevOps practices. Key topics covered include the benefits of continuous integration, deployment and delivery; the importance of testing including test-driven development; and embracing interdependence between developers and other IT roles. Best practices are noted to be situational and relationships must be respected.
The Essentials Of Test Driven Development Rock Interview
Test Driven Development is the fastest method to get software onto the market. Being one of the most used methods in the present business world, here is why the method is essential.
This document discusses using cloud testing for agile development. It introduces agile principles and practices like continuous integration. It then discusses how the cloud allows automated cross-browser testing across different browsers and platforms in parallel. This saves time compared to local testing. Cloud testing services can integrate with CI systems and provide detailed reports. They allow testing on many browser and OS combinations, mobile load testing, and integrating with monitoring tools.
** Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses **
This Edureka PPT on Software Testing Tutorial talks about different types of testing i.e. manual testing and automation testing approaches. Furthermore, it will also give you a brief insight on an automation Testing tool i.e. Selenium. Below topics are covered in this PPT:
Software Testing Overview
SDLC - Waterfall model, Spiral Model
Verification and Validation model
STLC
Types of Software testing
Software testing methods
Software Testing levels
Software testing documentation
Defect/bug life cycle-its importance
Automation testing - Why it is important?
Selenium
Selenium Locators
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
This document discusses agile testing processes. It outlines that agile is an iterative development methodology where requirements evolve through collaboration. It also discusses that testers should be fully integrated team members who participate in planning and requirements analysis. When adopting agile, testing activities like planning, automation, and providing feedback remain the same but are done iteratively in sprints with the whole team responsible for quality.
What designers can learn from (code) reviewIda Aalen
Everyone dreads “Design by committee”. Someone proofing your work might be a threat to creativity. But approaching digital design as a sole creative genius simply doesn’t work. Ida shares what she’s learned about collaboration from developers.
The document discusses software review methods and optimal review practices. It describes different review methods from walkthroughs to inspections and their goals and attributes. Inspections are highlighted as the most formal review method, involving preparation, an orientation, planning, a review meeting, rework, and verification stages. The goals of technical reviews are also outlined, including improving quality and knowledge while minimizing costs.
The document discusses automation testing and unit testing with JUnit. It defines automation testing as using a software to test a product by writing scripts to rerun test scenarios quickly. Unit testing tests individual software units in isolation to check for correct behavior. The document also describes Selenium as a tool for automating web application testing and JUnit as the most popular unit testing framework for Java. It notes the benefits of both automation and unit testing as reducing costs and bugs while improving quality.
Looking to move to Continuous Delivery? Worried about the quality of your the code? Helping your developers understand clean-code practices and getting the right testing strategy in place can take a while. What should you do to control the quality of the incoming code till then? This talk shares our experience of using PRRiskAdvisor to gradually educate and influence developers to write better code and also help the code reviewer to be more effective at their reviews.
Every time a developer raises a pull-request, PRRiskAdvisor analyzes the files that were changed and publishes a report on the pull request itself with the overall risk associated with this pull request and also risk associated with each file. It also runs static code analysis using SonarQube and publishes the configured violations as comments on the pull request. This way the reviewer just has to look at the pull request to get a decent idea of what it means to review this pull request. If there are too many violations, then PRRiskAdvisor can also automatically reject the pull request.
By doing this, we saw our developers starting paying more attention to clean code practices and hence the overall quality of the incoming code improved, while we worked on putting the right engineering practices and testing strategy in place.
More details: https://confengine.com/last-conference-canberra-2018/proposal/7294/improving-the-quality-of-incoming-code
Conference Link: https://2019.agileindia.org
Almost any application or software system manages data. It is hard to imagine test automation that is not affected by this fact. There are many differenct approaches how to prepare system under test, providing predefined test data: use application UI, invoke API methods, run business logic directly, access DB from test scenarios, etc. In this talk we will review most of existing approaches, starting from the easiest and the most popular ones and finishing with really tricky ways to manage your test data for large distributed systems. There is no ideal solution for every case or silver bullet, but I hope your toolset will become wider after visiting this talk.
This document discusses test driven development (TDD) for testers. It provides an overview of TDD, including writing tests before code, different types of tests, and the testing roles of developers versus testers. Developers are said to be "solution space" people who write unit and integration tests to drive code design, while testers are "problem space" people who focus on exploring potential problems and edge cases without limitations. Both developers and testers should work to avoid redundant testing and place the right types of tests in the right locations.
This document summarizes a concise QA and testing process developed for a small startup. It includes protocols for building, testing, managing changes, and releasing software. The build protocol ensures testing receives builds and information about changes. The test cycle protocol defines different types of testing cycles. The change protocol establishes feature freezes and code freezes to control changes late in development. The release protocol details the release approval and packaging process.
Pertanyaan dan jawaban (graham et.al 2011) part 3ikhwana luthfi
This document contains 5 multiple choice questions about software testing from a source titled "Graham et.al (2011)" along with the answers in Indonesian.
The questions cover topics like:
- Triggers for maintenance testing
- What testers should be doing when design documents are available
- The most effective testing technique for improving code maintainability
- Who is responsible for documenting issues in a formal review
- What type of issue is best found through static analysis
YouTube Link: https://youtu.be/cv6GvRCIuTs
** Test Automation Masters Program: https://www.edureka.co/masters-progra... **
This Edureka PPT on "What is Software Testing?" will give you a brief introduction to what software testing and all the basics concept related to software testing.
The following are the topics covered in the session:
Software Risks
What is Software Testing?
Principles of Sofware Testing
Software Testing Life Cycle
Dynamic Software Testing
Future of Sofware Testing
Follow us to never miss an update in the future.
YouTube: https://www.youtube.com/user/edurekaIN
Instagram: https://www.instagram.com/edureka_learning/
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
Castbox: https://castbox.fm/networks/505?country=in
Why Automated Testing Matters To DevOpsdpaulmerrill
“Automated testing is a pain in my ear! Why can’t QA get it right? Why do the tests keep breaking? And for Pete’s sake, stop blaming the infrastructure!”
…Ok, maybe you chose a different word than “ear”.
How often do you have thoughts like this? Daily?
Let’s talk about these frustrations, why they exist and how we can use them to improve our systems!
In this talk, Paul Merrill, founder and Principal Automation Engineer at Beaufort Fairmont explores why automated testing matters to DevOps. Join us to learn how automated testing can be a useful tool in the creation and release of your systems!
Working in many companies as consultant, delivery manager or tech lead I have always seen the same mistakes made in test automation process. I could count successful cases on fingers of one hand. Sometimes people don’t understand the true value of test automation, sometimes just could not organize this process spending lots of money and time without any significant result. I want to share 5 top mistakes aggregated from whole my practice and solutions I recommend for them.
What is the difference between manual testing and automation testingEr Mahednra Chauhan
Manual testing involves human testers executing test cases, while automation testing uses automation tools to run test cases. Manual testing is time-consuming and relies on human resources, whereas automated testing is significantly faster. While manual testing requires investment in human resources, automation testing requires investment in testing tools and automation engineers who have programming knowledge.
Coding and testing in Software EngineeringAbhay Vijay
The document discusses various aspects of software engineering coding practices. It describes the coding phase where design is transformed into code and tested. It emphasizes the importance of coding standards and guidelines to ensure uniform and understandable code. It also discusses code review, documentation, testing approaches like black box and white box testing, and the objectives of testing.
How will you benefit from auditing your code?
We prepared a summary of the most important advantages of performing a code audit.
Curious how to do it correctly? Click the link https://bit.ly/how-to-audit-your-code-li to check out a step by step guide, a checklist, and a sample report from an audit!
Basic of Software Testing. This presentation give course overview hosted on nimble e-learning platform.Presentation is just to give you brief overview of software testing.
The document discusses various topics related to technical interview questions for software testing. It covers software testing basics like the PDCA cycle and different testing types (white box, black box, gray box). It also discusses usability testing, defect categories, defining a testing policy, preparing acceptance plans, configuration management, code coverage tools, and different testing models. Key software development phases like design, coding, and their relative defect rates are examined. The roles of different testing teams and how test documents span the SDLC are outlined. Common testing concepts like test cases, logs, traceability, entry/exit criteria, verification vs validation are defined.
Testing and DevOps Culture: Lessons LearnedLB Denker
This document discusses the speaker's background and experiences with software engineering practices. It covers his education in computational mathematics and computer science, past roles at Universal Instruments developing machine software and at Google and Etsy implementing DevOps practices. Key topics covered include the benefits of continuous integration, deployment and delivery; the importance of testing including test-driven development; and embracing interdependence between developers and other IT roles. Best practices are noted to be situational and relationships must be respected.
The Essentials Of Test Driven Development Rock Interview
Test Driven Development is the fastest method to get software onto the market. Being one of the most used methods in the present business world, here is why the method is essential.
This document discusses using cloud testing for agile development. It introduces agile principles and practices like continuous integration. It then discusses how the cloud allows automated cross-browser testing across different browsers and platforms in parallel. This saves time compared to local testing. Cloud testing services can integrate with CI systems and provide detailed reports. They allow testing on many browser and OS combinations, mobile load testing, and integrating with monitoring tools.
** Software Testing Certification Courses: https://www.edureka.co/software-testing-certification-courses **
This Edureka PPT on Software Testing Tutorial talks about different types of testing i.e. manual testing and automation testing approaches. Furthermore, it will also give you a brief insight on an automation Testing tool i.e. Selenium. Below topics are covered in this PPT:
Software Testing Overview
SDLC - Waterfall model, Spiral Model
Verification and Validation model
STLC
Types of Software testing
Software testing methods
Software Testing levels
Software testing documentation
Defect/bug life cycle-its importance
Automation testing - Why it is important?
Selenium
Selenium Locators
Selenium playlist: https://goo.gl/NmuzXE
Selenium Blog playlist: http://bit.ly/2B7C3QR
This document discusses agile testing processes. It outlines that agile is an iterative development methodology where requirements evolve through collaboration. It also discusses that testers should be fully integrated team members who participate in planning and requirements analysis. When adopting agile, testing activities like planning, automation, and providing feedback remain the same but are done iteratively in sprints with the whole team responsible for quality.
What designers can learn from (code) reviewIda Aalen
Everyone dreads “Design by committee”. Someone proofing your work might be a threat to creativity. But approaching digital design as a sole creative genius simply doesn’t work. Ida shares what she’s learned about collaboration from developers.
The document discusses software review methods and optimal review practices. It describes different review methods from walkthroughs to inspections and their goals and attributes. Inspections are highlighted as the most formal review method, involving preparation, an orientation, planning, a review meeting, rework, and verification stages. The goals of technical reviews are also outlined, including improving quality and knowledge while minimizing costs.
This document discusses the relationship between testers and developers and how to improve interaction between the two roles. It notes that while they sometimes have a "love-hate" relationship as they have different expertise and goals, they ultimately depend on each other to ensure high quality software. The document provides tips for when testers and developers should interact, such as during design, test case reviews, and bug fixing. It also recommends ways to build trust between testers and developers through clear communication and establishing processes for quality control.
Code review is an inspection process where developers examine code samples to identify and fix defects. It helps ensure good code quality by allowing experienced developers to share knowledge with less experienced ones. Benefits include more stable products with fewer bugs due to improved code structure, standards and focus on new features rather than fixing issues. Issues that can arise include developers not following through on review comments, lack of buy-in, unrealistic expectations and peer fear. Various review types and tools can help address these issues.
code_review_checklist_6_actions_to_improve_the_quality_of_your_reviews.pdfsarah david
Elevate code quality with our optimal Code Review Checklist! Uncover issues, boost security, and enhance performance. Developers waiting four days for reviews? Our research exposes pitfalls like "Looks Good to Me" comments. Optimize workflows, automate reviews, and accelerate delivery. Survey shows 60% find reviews valuable but face bottlenecks. Our blog reveals the Checklist: Procedure, six steps, and best practices. Benefits include problem discovery and enhanced security. Dive in for a streamlined approach with our proven checklist, overcoming challenges for consistent, high-quality results.
code_review_checklist_6_actions_to_improve_the_quality_of_your_reviews.pptxsarah david
Elevate code quality with our optimal Code Review Checklist! Uncover issues, boost security, and enhance performance. Developers waiting four days for reviews? Our research exposes pitfalls like "Looks Good to Me" comments. Optimize workflows, automate reviews, and accelerate delivery. Survey shows 60% find reviews valuable but face bottlenecks. Our blog reveals the Checklist: Procedure, six steps, and best practices. Benefits include problem discovery and enhanced security. Dive in for a streamlined approach with our proven checklist, overcoming challenges for consistent, high-quality results.
Ben Walters - Creating Customer Value With Agile Testing - EuroSTAR 2011TEST Huddle
EuroSTAR Software Testing Conference 2011 presentation on Creating Customer Value With Agile Testing by Ben Walters. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Peer code review is one of the most effective ways to find defects – but is it agile? Because agile teams loathe heavy process, code review practices can easily fail. However, lightweight peer code review aligns well with the central tenets of agile—keeping feedback close to the point of creation, increasing team velocity by finding defects faster, and improving collective code ownership through frequent collaboration. Gregg Sporar shares recent research on code review practices and describes an agile code review approach—how much time to spend, which code to review, how much code to review at a time, how to set goals, the value of annotation, and more. After comparing four styles of code review—pair programming, over-the-shoulder, email, and tool-assisted—Gregg gives specific advice for creating review checklists and dealing with the social effects of code review in an agile environment.
Mastering Agile Practices to Build High Performing TeamsAgileThought
These slides are from a talk that I gave to the Tampa Bay Agile Meetup on August 19, 2014. The talk was titled "Mastering Agile Practices to Build High Performing Teams". http://www.meetup.com/tampa-bay-agile/events/193898502/
Description:
You've read the books. You already know what your Agile team SHOULD be doing. Your Daily Standup meeting should be short and sweet. Your deployments should be automated. Your Sprint Retrospectives should inspire improvement.
So if you know what to do, why aren't you doing it?
The short answer is because Agile is hard. It takes real discipline and leadership to master even the most basic practices. Many teams have committed to adopting Agile, but they just don’t know how to get to the next level.
In this talk, I will share my real world experiences from years of coaching high performing Agile teams. I will discuss the key practices that must be mastered for a team to become great. Additionally, I will identify useful measurement techniques so that teams know if they are improving.
Software Defect Prevention via Continuous InspectionJosh Gough
Research and guidance for educing software development risk and cost while improving speed, quality and maintainability by applying review at all levels.
This document discusses agile testing and its principles. It defines agile testing as testing practices that follow the agile manifesto and treat development as the customer of testing. The key principles of agile testing are that individuals and interactions are valued over processes, working software is valued over documentation, and responding to change is valued over following a plan. It also discusses specific agile development methodologies like extreme programming and the role of testing in agile projects.
This presentation includes challenges in testing, levels of testing, best practices and policies, Test Drive Design(TDD),
Behavioral Driven Design (BDD Testing), TDD v/s BDD
The document discusses principles and best practices for code review. It describes the need for code review to improve quality and find bugs. It covers different types of code review including formal, informal, pair programming, and tool-assisted. The document provides guidance on the scope of a code review including goals, APIs, maintainability, security, integration and testing. It also discusses automated code review tools and common mistakes to check for such as exception handling errors.
An introduction to Software Testing and Test ManagementAnuraj S.L
The document provides an introduction to software testing and test management. It discusses key concepts like quality, software testing definitions, why testing is important, who does testing, what needs to be tested, when testing is done, and testing standards. It also covers testing methodologies like black box and white box testing and different levels of testing like unit testing, integration testing, and system testing. The document is intended to give a basic overview of software testing and related topics.
The document discusses testing concepts such as code with tests vs without tests, test-oriented development, and different types of testing including unit testing, integration testing, and acceptance testing. It provides examples of test-driven development (TDD) and behavior-driven development (BDD) processes. The document also discusses tips for testing, including only testing what is necessary and identifying the appropriate types of testing for an application. Frameworks and tools for test automation and continuous integration are also mentioned.
Behavior Driven Development—A Guide to Agile Practices by Josh EastmanQA or the Highway
The document discusses Behavior Driven Development (BDD) and how it can help increase quality and prepare an organization for increased business demands. It describes BDD as an industry practice where the whole team collaborates on system testing and definition of done. BDD promotes requirements using examples, collaboration between roles, finding defects earlier and more often through automation, and keeping technical debt low.
The document provides an overview of software testing and quality assurance concepts. It defines key terms like software, software testing, quality assurance, and validation and verification. It describes the objectives and types of testing like static and dynamic analysis. It also discusses quality factors, metrics, statistical quality control methods like control charts, and total quality management approaches.
Similar to Let's review it: What designers can learn from (code) review (20)
- In March 2020, during the COVID-19 pandemic, the remote-friendly startup Confrere saw a dramatic increase in usage, with weekly active users increasing 10x and the number of video calls increasing 100x. Confrere handled 96% of video consultations in Norway during this period.
- Previously, Confrere had focused on building their product for physicians with a small budget and team. They visited over 10% of doctors' offices in Norway to better understand user needs without dedicated research teams.
- The Core Model of identifying core pages that achieve business goals and complete user tasks helped Confrere create effective, timeless content and align their efforts despite limited resources. This content supported their rapid growth during
Presented at Berlin.js May 31st 2018 for the #jsconfeu Special. Almost every video call begins with the same clumsy questions. Can you hear me now? Did I just turn off my camera instead of my mic now? But what if we could take the awkward troubleshooting out of the conversation, and solve it with code instead? In this talk, Ingvild Indrebø will give you a glimpse into aspects of WebRTC, WebAudio and Canvas, by showing you how she used these technologies to build a user-friendly and accessible tool to make sure you’re all set for your video call.
Enkel og effektiv brukertesting (andvändartesting)Ida Aalen
Ida Aalen viser 7 enkle og effektive teknikker for å gjøre brukertesting med lite tid, lite penger og lite ressurser. Ida er CPO i Confrere. Presentasjon på DCongress 8. mars 2018.
The document discusses 7 low-cost usability testing methods that can be used at different stages of a project: 1) Hit the streets, 2) Information architecture, 3) First click, 4) Live experiments, 5) Did you get it done, 6) Microtesting content, and 7) Weekly drop-in lab test. Each method is described in terms of the time and cost required to implement it. The document advocates for incorporating usability testing into project plans from the beginning and testing with actual users rather than colleagues. It provides guidance on setting up a usability testing lab and conducting regular weekly testing sessions.
My Fashion PPT is my presentation on fashion and TrendssMedhaRana1
This Presentation is in one way a guide to master the classic trends and become a timeless beauty. This will help the beginners who are out with the motto to excel and become a Pro Fashionista, this Presentation will provide them with easy but really useful ten ways to master the art of styles. Hope This Helps.
TRENDS IN SOLID WASTE MANAGEMENT Digital Technologies can play a crucial role in making Metro Rizal's waste management systems more circular and sustainable
11. “Code review is systematic examination […] of
computer source code. It is intended to find mistakes
overlooked in software development, improving the
overall quality of software. Reviews are done in various
forms such as pair programming, informal
walkthroughs, and formal inspections.
Wikipedia
13. Pull request submitted by ingvilin
#423 Add onboarding status
To keep track of the
onoardingProgress a default
onboarding progress object is
added to the users metadata on
completing the sign up process.
ingvilin requested a review from
daginge
22. “Code reviews set the tone for the entire company that
everything we do should be open to scrutiny from
others, and that such scrutiny should be a welcome
part of your workflow rather than viewed as
threatening.
Bruce Johnson, co-founder of Full Story
23. “Code reviews set the tone for the entire company that
everything we do should be open to scrutiny from
others, and that such scrutiny should be a welcome
part of your workflow rather than viewed as
threatening.
Me
64. Review walkthroughs
• Walkthrough is done together
• One person in charge of reviewing and documenting
• Choose a format that gives as much context as possible
• The idea is to identify issues, not necessarily solve them