Techdaysnl - code review features in tfs vnext
•
0 likes•578 views
The document discusses code review processes and tools, outlining scenarios for pre-check in and post-check in reviews, how code review workflows work in tools like Team Review and TFS Code Review Workflow, and providing links to documentation and demos on configuring code reviews in Microsoft's Team Foundation Server. It also notes that sometimes external subject matter experts need to be involved in reviews and that geographical or timing constraints may require reviews without developers sitting together.
Report
Share
Report
Share
Recommended
Fran O'Hara - Evolving Agile Testing - EuroSTAR 2012
EuroSTAR Software Testing Conference 2012 presentation on Evolving Agile Testing by Fran O'Hara. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Reviews checklists
The document discusses software quality assurance reviews and checklists. It describes different types of reviews including inspections and walkthroughs. It outlines the benefits of reviews in finding defects early and decreasing costs. Reviews should have documentation of any issues found and analysis to improve the development process. Checklists are recommended to focus reviews on common error types.
Test cases and bug report v3.2
The document discusses test cases, defects (bugs), and bug reports. It provides definitions and examples of test cases, their purpose and components. Examples of test management tools and test-driven development are also presented. Defects and what constitutes a good bug report are defined. The importance of collaboration between testers and developers is emphasized.
Finding bugs, categorizing bugs and writing good bug reports
The document discusses finding, categorizing, and reporting bugs. It provides guidance on finding critical bugs by thoroughly understanding the application, using incorrect data types, load testing, and testing across browsers. Bugs should be categorized based on their priority and severity. Priority indicates how quickly a bug needs to be fixed, while severity represents the importance of fixing it. A good bug report includes steps to reproduce, expected results, and actual results. Popular bug tracking tools like Trac, Zoho, Bloodhound, Bugzilla, and TFS are also briefly mentioned.
Program Check List (PCL) FSOFT
PCL: Programming Check List (UT Test case)
PCL: Used in Unit Test Stage
PCL: Done by Developers
PCL: Used to check code following step by step
Bug Advocacy
1. The document discusses the concept of "bug advocacy", which is the practice of writing bug reports in a way that motivates programmers to fix the bug.
2. Effective bug reports motivate programmers by highlighting how serious or widespread the bug is. They also overcome objections by providing clear reproduction steps and evidence of customer impact.
3. The document recommends testing around found bugs to prove they are more serious or common than initially thought. This includes varying your own actions, program settings, and software/hardware environment to trigger related or worse failures. The goal is to sell programmers on the importance of fixing the bug.
Specification by example and agile acceptance testing
Specification by example and agile acceptance testing, presentation given to HSBC developers on 21/09/09 for more info see http://specificationbyexample.com
Writing Test Cases From User Stories And Acceptance Criteria
The acceptance criteria provides the majority of what needs to be tested from the user story. To achieve maximum test coverage, time should be taken to consider the workflow, boundaries, and negative scenarios based on the acceptance criteria. Writing test cases in this way can help identify requirement gaps, prevent code re-work, and save the entire team from unnecessary headaches by ensuring the test cases remain up-to-date and address all aspects of the user story.
Recommended
Fran O'Hara - Evolving Agile Testing - EuroSTAR 2012
EuroSTAR Software Testing Conference 2012 presentation on Evolving Agile Testing by Fran O'Hara. See more at: http://conference.eurostarsoftwaretesting.com/past-presentations/
Reviews checklists
The document discusses software quality assurance reviews and checklists. It describes different types of reviews including inspections and walkthroughs. It outlines the benefits of reviews in finding defects early and decreasing costs. Reviews should have documentation of any issues found and analysis to improve the development process. Checklists are recommended to focus reviews on common error types.
Test cases and bug report v3.2
The document discusses test cases, defects (bugs), and bug reports. It provides definitions and examples of test cases, their purpose and components. Examples of test management tools and test-driven development are also presented. Defects and what constitutes a good bug report are defined. The importance of collaboration between testers and developers is emphasized.
Finding bugs, categorizing bugs and writing good bug reports
The document discusses finding, categorizing, and reporting bugs. It provides guidance on finding critical bugs by thoroughly understanding the application, using incorrect data types, load testing, and testing across browsers. Bugs should be categorized based on their priority and severity. Priority indicates how quickly a bug needs to be fixed, while severity represents the importance of fixing it. A good bug report includes steps to reproduce, expected results, and actual results. Popular bug tracking tools like Trac, Zoho, Bloodhound, Bugzilla, and TFS are also briefly mentioned.
Program Check List (PCL) FSOFT
PCL: Programming Check List (UT Test case)
PCL: Used in Unit Test Stage
PCL: Done by Developers
PCL: Used to check code following step by step
Bug Advocacy
1. The document discusses the concept of "bug advocacy", which is the practice of writing bug reports in a way that motivates programmers to fix the bug.
2. Effective bug reports motivate programmers by highlighting how serious or widespread the bug is. They also overcome objections by providing clear reproduction steps and evidence of customer impact.
3. The document recommends testing around found bugs to prove they are more serious or common than initially thought. This includes varying your own actions, program settings, and software/hardware environment to trigger related or worse failures. The goal is to sell programmers on the importance of fixing the bug.
Specification by example and agile acceptance testing
Specification by example and agile acceptance testing, presentation given to HSBC developers on 21/09/09 for more info see http://specificationbyexample.com
Writing Test Cases From User Stories And Acceptance Criteria
The acceptance criteria provides the majority of what needs to be tested from the user story. To achieve maximum test coverage, time should be taken to consider the workflow, boundaries, and negative scenarios based on the acceptance criteria. Writing test cases in this way can help identify requirement gaps, prevent code re-work, and save the entire team from unnecessary headaches by ensuring the test cases remain up-to-date and address all aspects of the user story.
Bug life cycle
The document discusses the bug life cycle and defect reporting process. It defines what a bug is and outlines the typical stages a defect goes through from initial reporting as "New" to being ultimately "Closed" after being addressed. Key stages include assignment to a developer, the developer fixing and testing the fix, reopening if needed, and closing once resolved. Defects can also be rejected, deferred, or marked as duplicates. Reporting is typically done through a standardized defect report form that captures details to help reproduce and resolve the issue. Project management tools can also be used to log and track defects.
Bug reporting and tracking
The document discusses defect reporting and tracking. It defines a software bug and explains that once a tester identifies a defect, they generate a formal defect report. The report includes information like a unique ID, project name, summary, steps to reproduce, actual and expected results. A bug goes through different statuses in its lifecycle from new to closed. Developers analyze and fix bugs, while testers verify fixes and may reopen bugs. Bug tracking systems help teams manage large numbers of defects by keeping track of key details for each bug report.
Fagan Inspection
Fagan Inspection is a rigorous quality control technique invented in the 1970s for inspecting software documents to find defects. It involves a team reviewing a document using a structured process with defined roles. The process includes planning, an overview meeting, individual preparation, the inspection meeting, defect analysis, rework, and follow up. When performed properly it is very effective at finding defects early. However, inspections are rarely used due to professional and organizational ignorance, difficulties in implementation, and intangible perceived benefits. Making inspections work requires addressing these challenges.
Bug life cycle
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
How to report bugs
The document provides guidance on writing effective bug reports to help ensure bugs get fixed. Key points include:
1) Bug reports should be reproducible, specific, and assign a unique identifier.
2) Clearly specify steps to reproduce the bug, expected results, and actual results.
3) Use a standardized template to maintain consistency and provide necessary details about the bug.
Speed up your tests
To speed up tests, identify and isolate flaky tests, fix their root causes, and monitor them continuously. Tests can also be parallelized by running independent tests on multiple VMs simultaneously using tools like Selenium Grid. Break suites into focused suites like smoke and regression. Create smart test data programmatically via APIs or databases for reliability and speed. Use direct locators like IDs over generic XPaths. Add conditional waits instead of generic waits to tests. Unit testing is a shared responsibility between devs and QA.
How to Deliver the Right Software (Specification by example)
Talk about Specification by Example. What's the problems it tries to tackle and how to solve them.
I gave this talk at findmypast.com on a "lunch and learn" weekly meeting for the company.
This is a new version of my previous presentation about "Specification by example"
http://www.slideshare.net/AsierBarrenetxea1/specification-by-example-33594438
To Automate or Not to Automate
WEBINAR- To Automate or Not to Automate: 5 Things to Consider when Building Your Test Automation Strategy
In this webinar Data Science Manager at RainforestQA, Maciej Gryka, shares how teams determine when to use automation and when humans are needed to deliver amazing customer experiences.
Access the webinar via this link: http://ht.ly/hfTi30jrIlC
Software Testing - Defect/Bug Life Cycle - Complete Flow Chart of Defect States
The document discusses the bug life cycle in software development. It defines a bug as abnormal software behavior and explains that bugs go through various states as part of a standardized life cycle process. The states are new, open, assign, test, verified, deferred, reopened, duplicate, rejected, and closed. Each state is described in terms of when a bug attains that label and what it means for the bug resolution process.
Compare squish tool vs telerik tool
Squish is a cross-platform automated testing tool that supports desktop, mobile, web and embedded platforms. It has powerful recording and scripting capabilities using languages like Python, JavaScript, Perl, Tcl and Ruby. Squish has a large customer base of over 3000 companies including Google, IBM, HP and Boeing. Licensing costs around €6900-€7440 for a one or two person license that includes the first year of support and updates. Squish can integrate with build tools like Jenkins and supports scripting tests in both code and visually using its IDE. It allows for data driven, remote and BDD style testing across multiple browsers and platforms.
Software testing tools (free and open source)
This document discusses various tools used for test automation including Cobertura, Selenium, JMeter, Bugzilla, and Testia Tarantula. Cobertura is a code coverage tool that calculates test coverage percentages. Selenium is described as a tool for automating web application testing across browsers. JMeter is introduced as a load testing tool focused on analyzing performance of web applications. Bugzilla and Tarantula are mentioned as tools for bug tracking and project/test management respectively in agile software development. The document also discusses integrating these various tools together for a complete test automation framework.
Pm training (planning and tracking) - Project Leader Ramp-Up
Course Objective
The purpose of this course is to make a short summary about the Fsoft processes & practices to be used in the project context.
This course is not aimed to replace the normal training courses.
Spec by-example
Specification by example is a technique that has the following key benefits: less rework, higher product quality, more efficient implementation of changes, and better alignment across roles. It involves deriving system scope from goals, specifying collaboratively using examples, refining the specification, and automating validation to evolve a living documentation system. The document discusses practices for each step, including deriving requirements from goals by asking "why", using workshops and examples to specify collaboratively, refining specifications through iteration, and automating tests from examples to continuously validate the system.
Unfuddle usage guide 2
The document provides a workflow for developers and QA to follow when working on tickets in Unfuddle. The workflow involves developers estimating tickets, updating statuses, writing tests and code, and resolving tickets once development is complete. QA then tests resolved tickets, failing them back to developers if issues are found or passing them to customers if testing is successful.
Presentation On Software Testing Bug Life Cycle
The document defines a bug as abnormal software behavior and discusses the bug lifecycle. It states bugs go through different states including new, open, assigned, test, verified, deferred, reopened, rejected, and closed. The states are part of a standardized process to ensure bugs are addressed and closed. Testers report bugs to programmers using problem report forms to fully explain how to reproduce the problem with a minimum number of steps so it can be understood and fixed.
Bug Advocacy
GTech Technology Focus Group organised an event on "Trends and Transformations on Quality Assurance & Quality Control"
Automation testing introduction for FujiNet
This document discusses automation testing and provides an overview of manual vs automation testing. It covers why automation testing is important, including allowing repetitive tests to run across multiple builds and reducing human error. Common automation tools like QTP and Selenium are mentioned. The history of automation from record and playback to modern keyword-driven approaches is summarized. Examples of building automation frameworks for QTP and Selenium are provided. In conclusion, the document promotes automation testing as important for the future.
Debbuging
Debugging is the process of finding and fixing bugs in a computer program. There are three main types of bugs: syntactic errors due to incorrect code syntax, semantic errors due to logical errors, and algorithmic errors where the overall program design is flawed. Debuggers are software tools used to test programs and locate errors by allowing programmers to trace execution, set breakpoints, and monitor variables. Common debugging techniques include unit testing, print statements, stepping through code, and checking for interface and boundary issues.
VodQA3_ATDD_KetanSoni
This was a full length talk presented by Ketan Soni in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
Lesson 4...Bug Life Cycle
A bug is an unexpected behavior in software that hinders its functionality. Test cases are used to find bugs by executing steps and observing outputs. When a bug is found, it is reported to developers and tracked through statuses like new, assigned, open, fixed, and closed as developers work to resolve it. Statuses indicate whether a bug is being investigated, in progress, fixed, or resolved.
SPCA2013 - Test-driven Development with SharePoint 2013 and Visual Studio
This document discusses test-driven development (TDD) approaches for SharePoint projects using Visual Studio. It begins with an introduction to TDD and the benefits it provides. It then covers different types of tests like unit, integration, and acceptance tests. It demonstrates how to write server-side and client-side tests for SharePoint. Finally, it discusses test automation tools and concludes that while SharePoint presents challenges for testing, TDD is still very valuable when developing for the platform.
Overcome-3-common-aem-delivery-challenges
AEM Maxed = Agile + Automation.
Time Warner Cable and iCiDIGITAL reveal how a stellar agile development team delivers an award-winning website using Adobe Experience Manager. Highlights include team interactions, scaling the team, collaborative moments, testing automation, and continuous integration. Also, they will share previews of a few open source attractions that will accelerate your Adobe Experience Manager delivery.
More Related Content
What's hot
Bug life cycle
The document discusses the bug life cycle and defect reporting process. It defines what a bug is and outlines the typical stages a defect goes through from initial reporting as "New" to being ultimately "Closed" after being addressed. Key stages include assignment to a developer, the developer fixing and testing the fix, reopening if needed, and closing once resolved. Defects can also be rejected, deferred, or marked as duplicates. Reporting is typically done through a standardized defect report form that captures details to help reproduce and resolve the issue. Project management tools can also be used to log and track defects.
Bug reporting and tracking
The document discusses defect reporting and tracking. It defines a software bug and explains that once a tester identifies a defect, they generate a formal defect report. The report includes information like a unique ID, project name, summary, steps to reproduce, actual and expected results. A bug goes through different statuses in its lifecycle from new to closed. Developers analyze and fix bugs, while testers verify fixes and may reopen bugs. Bug tracking systems help teams manage large numbers of defects by keeping track of key details for each bug report.
Fagan Inspection
Fagan Inspection is a rigorous quality control technique invented in the 1970s for inspecting software documents to find defects. It involves a team reviewing a document using a structured process with defined roles. The process includes planning, an overview meeting, individual preparation, the inspection meeting, defect analysis, rework, and follow up. When performed properly it is very effective at finding defects early. However, inspections are rarely used due to professional and organizational ignorance, difficulties in implementation, and intangible perceived benefits. Making inspections work requires addressing these challenges.
Bug life cycle
BugRaptors provide Software testing is entirely about finding defects in applications, right? Apparently, this can be considered as the principal goal of all the QA practices. However, all the defects diverge from each other. It cannot be stated if some are more important than others, yet it’s possible to locate and fix them all.
How to report bugs
The document provides guidance on writing effective bug reports to help ensure bugs get fixed. Key points include:
1) Bug reports should be reproducible, specific, and assign a unique identifier.
2) Clearly specify steps to reproduce the bug, expected results, and actual results.
3) Use a standardized template to maintain consistency and provide necessary details about the bug.
Speed up your tests
To speed up tests, identify and isolate flaky tests, fix their root causes, and monitor them continuously. Tests can also be parallelized by running independent tests on multiple VMs simultaneously using tools like Selenium Grid. Break suites into focused suites like smoke and regression. Create smart test data programmatically via APIs or databases for reliability and speed. Use direct locators like IDs over generic XPaths. Add conditional waits instead of generic waits to tests. Unit testing is a shared responsibility between devs and QA.
How to Deliver the Right Software (Specification by example)
Talk about Specification by Example. What's the problems it tries to tackle and how to solve them.
I gave this talk at findmypast.com on a "lunch and learn" weekly meeting for the company.
This is a new version of my previous presentation about "Specification by example"
http://www.slideshare.net/AsierBarrenetxea1/specification-by-example-33594438
To Automate or Not to Automate
WEBINAR- To Automate or Not to Automate: 5 Things to Consider when Building Your Test Automation Strategy
In this webinar Data Science Manager at RainforestQA, Maciej Gryka, shares how teams determine when to use automation and when humans are needed to deliver amazing customer experiences.
Access the webinar via this link: http://ht.ly/hfTi30jrIlC
Software Testing - Defect/Bug Life Cycle - Complete Flow Chart of Defect States
The document discusses the bug life cycle in software development. It defines a bug as abnormal software behavior and explains that bugs go through various states as part of a standardized life cycle process. The states are new, open, assign, test, verified, deferred, reopened, duplicate, rejected, and closed. Each state is described in terms of when a bug attains that label and what it means for the bug resolution process.
Compare squish tool vs telerik tool
Squish is a cross-platform automated testing tool that supports desktop, mobile, web and embedded platforms. It has powerful recording and scripting capabilities using languages like Python, JavaScript, Perl, Tcl and Ruby. Squish has a large customer base of over 3000 companies including Google, IBM, HP and Boeing. Licensing costs around €6900-€7440 for a one or two person license that includes the first year of support and updates. Squish can integrate with build tools like Jenkins and supports scripting tests in both code and visually using its IDE. It allows for data driven, remote and BDD style testing across multiple browsers and platforms.
Software testing tools (free and open source)
This document discusses various tools used for test automation including Cobertura, Selenium, JMeter, Bugzilla, and Testia Tarantula. Cobertura is a code coverage tool that calculates test coverage percentages. Selenium is described as a tool for automating web application testing across browsers. JMeter is introduced as a load testing tool focused on analyzing performance of web applications. Bugzilla and Tarantula are mentioned as tools for bug tracking and project/test management respectively in agile software development. The document also discusses integrating these various tools together for a complete test automation framework.
Pm training (planning and tracking) - Project Leader Ramp-Up
Course Objective
The purpose of this course is to make a short summary about the Fsoft processes & practices to be used in the project context.
This course is not aimed to replace the normal training courses.
Spec by-example
Specification by example is a technique that has the following key benefits: less rework, higher product quality, more efficient implementation of changes, and better alignment across roles. It involves deriving system scope from goals, specifying collaboratively using examples, refining the specification, and automating validation to evolve a living documentation system. The document discusses practices for each step, including deriving requirements from goals by asking "why", using workshops and examples to specify collaboratively, refining specifications through iteration, and automating tests from examples to continuously validate the system.
Unfuddle usage guide 2
The document provides a workflow for developers and QA to follow when working on tickets in Unfuddle. The workflow involves developers estimating tickets, updating statuses, writing tests and code, and resolving tickets once development is complete. QA then tests resolved tickets, failing them back to developers if issues are found or passing them to customers if testing is successful.
Presentation On Software Testing Bug Life Cycle
The document defines a bug as abnormal software behavior and discusses the bug lifecycle. It states bugs go through different states including new, open, assigned, test, verified, deferred, reopened, rejected, and closed. The states are part of a standardized process to ensure bugs are addressed and closed. Testers report bugs to programmers using problem report forms to fully explain how to reproduce the problem with a minimum number of steps so it can be understood and fixed.
Bug Advocacy
GTech Technology Focus Group organised an event on "Trends and Transformations on Quality Assurance & Quality Control"
Automation testing introduction for FujiNet
This document discusses automation testing and provides an overview of manual vs automation testing. It covers why automation testing is important, including allowing repetitive tests to run across multiple builds and reducing human error. Common automation tools like QTP and Selenium are mentioned. The history of automation from record and playback to modern keyword-driven approaches is summarized. Examples of building automation frameworks for QTP and Selenium are provided. In conclusion, the document promotes automation testing as important for the future.
Debbuging
Debugging is the process of finding and fixing bugs in a computer program. There are three main types of bugs: syntactic errors due to incorrect code syntax, semantic errors due to logical errors, and algorithmic errors where the overall program design is flawed. Debuggers are software tools used to test programs and locate errors by allowing programmers to trace execution, set breakpoints, and monitor variables. Common debugging techniques include unit testing, print statements, stepping through code, and checking for interface and boundary issues.
VodQA3_ATDD_KetanSoni
This was a full length talk presented by Ketan Soni in vodQA-3 : A QA Meet held in ThoughtWorks, Pune.
Lesson 4...Bug Life Cycle
A bug is an unexpected behavior in software that hinders its functionality. Test cases are used to find bugs by executing steps and observing outputs. When a bug is found, it is reported to developers and tracked through statuses like new, assigned, open, fixed, and closed as developers work to resolve it. Statuses indicate whether a bug is being investigated, in progress, fixed, or resolved.
What's hot (20)
How to Deliver the Right Software (Specification by example)
How to Deliver the Right Software (Specification by example)
Software Testing - Defect/Bug Life Cycle - Complete Flow Chart of Defect States
Software Testing - Defect/Bug Life Cycle - Complete Flow Chart of Defect States
Pm training (planning and tracking) - Project Leader Ramp-Up
Pm training (planning and tracking) - Project Leader Ramp-Up
Similar to Techdaysnl - code review features in tfs vnext
SPCA2013 - Test-driven Development with SharePoint 2013 and Visual Studio
This document discusses test-driven development (TDD) approaches for SharePoint projects using Visual Studio. It begins with an introduction to TDD and the benefits it provides. It then covers different types of tests like unit, integration, and acceptance tests. It demonstrates how to write server-side and client-side tests for SharePoint. Finally, it discusses test automation tools and concludes that while SharePoint presents challenges for testing, TDD is still very valuable when developing for the platform.
Overcome-3-common-aem-delivery-challenges
AEM Maxed = Agile + Automation.
Time Warner Cable and iCiDIGITAL reveal how a stellar agile development team delivers an award-winning website using Adobe Experience Manager. Highlights include team interactions, scaling the team, collaborative moments, testing automation, and continuous integration. Also, they will share previews of a few open source attractions that will accelerate your Adobe Experience Manager delivery.
Case Study: Time Warner Cable's Formula for Maximizing Adobe Experience Manager
Time Warner Cable and iCiDIGITAL reveal how a stellar agile development team delivers an award-winning website using Adobe Experience Manager. Highlights include team interactions, scaling the team, collaborative moments, testing automation, and continuous integration. Also, they share previews of a few open source attractions that will accelerate your Adobe Experience Manager delivery.
Agile testing
Despite the belief that a shared context and collaboration drives quality, too often, software testers and quality professionals struggle to find their place within today's integrated agile teams. This session is a practitioner’s view of testing and testing practices within an iterative/incremental development environment. We will begin with a discussion of some of the challenges of testing within an agile environment and delve into the guiding principles of Agile Testing and key enabling practices. Agile Testing necessitates a change in mindset, and it is as much, if not more, about behavior, as it is about skills and tooling, all of which will be explored.
How to run an Enterprise PHP Shop
This talk was geared around the concept of showing developers what goes into getting enterprise products out the door. Unit testing, release process, continuous integration, security, social engineering, bug bashes.
Code Review
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.
Productivity gains with Visual Studio ALM.PPTX
This document discusses how a company is using Team Foundation Server (TFS) to improve their project management and development processes. It outlines some common pain points teams face around requirements management, feedback, project visibility, code quality, and testing. It then describes how TFS can address these issues through features like requirement tracking, feedback collection, work item reports, gated check-ins, code metrics, code reviews, lab management, and more. The final section shows how TFS editions like Premium and Ultimate provide additional capabilities for tasks like architecture validation, debugging production issues, and memory leak analysis.
Introduction to Parasoft C++TEST
Static Code Analysis, Dynamic Application Monitoring, Code Coverage and Unit testing as a combined method in Software Error Prevention process.
Portal Deployment Best Practices | IBM Portal Excellence Conference 2009
Michael Porter, Principal, Portal and Collaboration Solutions at Perficient, presented at the IBM Portal Excellence Conference, Tuesday, October 13, 2009.
Successful portal projects depend on aligning your business needs to the technology and then using common best practices to run a successful project. In this session we will discuss how to align your business needs to create a portal solution and
then running a successful project by taking a holistic approach to portal. Topics will include solution roadmap, portal
governance, common technologies to include, and project management best practices that will make your project a success from a business and technical perspective.
Agile & DevOps - It's all about project success
The document provides information on DevOps practices and tools from Microsoft. It discusses how DevOps enables continuous delivery of value through integrating people, processes, and tools. Benefits of DevOps include more frequent and stable releases, lower change failure rates, and empowered development teams. The document provides examples of DevOps scenarios and recommends discussing solutions and migration plans with Microsoft.
Test team dynamics, Антон Мужайло
The document discusses building an effective test team. It recommends hiring people with a mix of hard and soft skills at different experience levels who share common goals and are willing to teach and learn from each other. Soft skills like learning, sharing knowledge, explaining viewpoints, negotiating, and handling conflicts are emphasized as being more important than hard skills. The document provides examples of how to define needed hard skills and evaluate candidates based on their skills and experience levels. It also shows an example skills assessment of potential candidates for both manual and automation testing roles.
Expo qa15 Keynote
The document discusses the need for a holistic view when scaling agile organizations. It covers topics like the problems of scaling agile, what constitutes a scaled agile organization, and how individuals can contribute to its success. The keynote speaker advocates adopting a networked structure over hierarchical ones and emphasizes quality being everyone's responsibility through cross-functional teams and a whole product focus.
Quality Jam: BDD, TDD and ATDD for the Enterprise
During Quality Jam 2016 I had the privilege of presenting with one of QASymphony's earliest customers, Better Cloud, on how methodologies like BDD, TDD and ATDD scale for the enterprises. Adam Satterfield is the VP of Quality Assurance at Bettercloud and has been in QA for many years; he has taught me a lot about Behavior Driven Development, Test Driven Development, Acceptance Test Driven Development. In the session we share a new way of testing-- what Adam and I believe to be the next generation of testing development.
We know that there are several ways to do testing and we are just showing one new way to do it - If this session doesn't inspire action, hopefully it will at least give you and your team something to think about.
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Data flow analysis is a type of static code analysis that examines how values are propagated through a program. It is more effective than pattern matching or regular static analysis at finding defects related to interactions between methods and classes that may be difficult to uncover through testing alone. Static analysis tools using data flow analysis can simulate execution paths to detect potential issues without requiring the code to be compiled and run. Developers are encouraged to use static testing tools to catch defects early in development, as prevention of bugs is more efficient than finding and fixing them later.
Validation
This document provides an overview and summary of a presentation on validation. It outlines the following key points:
1) Section A of the presentation covers topics related to validation processes, including approaches to software and process validation, validation throughout the product lifecycle, documentation requirements, and statistical techniques.
2) Section B addresses ordering details, costs, and product delivery. The presentation can be purchased for $49 and downloaded from the provided website. It is licensed for single facility use and includes security features to control distribution.
3) The presentation is an educational tool that steps through validation requirements and regulations over approximately 4 minutes. It includes notes and is intended to be reused for training purposes within the purchasing facility.
Quality Assurance & Testing in a glimpse
This presentation slide has been made in respect of our local market, demand, practice and scope for the beginners in Bangladesh.
There are many things which are need to be discussed widely, cause the points mentioned here are not covering all the stuff as it shown and in some places it depends on context and contradictory thoughts may arise unless you feel free to discuss. I just wanted to give a glimpse giving an Option to everyone to participate the presentation...
Making the Move to Behavior Driven Development
The document discusses moving to a behavior-driven development (BDD) approach. It outlines challenges with traditional software development processes, such as requirements getting lost in handoffs. BDD aims to address these by shifting testing to the beginning through acceptance tests written in a "Given-When-Then" format. This allows teams to build testable code, catch issues earlier, and deploy features incrementally. Adopting BDD requires training, champion support, and patience. Metrics should track success, and teams can start small before a full rollout.
Successful Software Projects - What you need to consider
A successful software project is much more than just getting the code to compile and run. Building a successful piece of software requires multiple stages of planning and execution. The success or failure of the project will depend as much upon the processes used for development the project as the final project itself. This presentation is a high level survey of key processes and considerations that should be addressed for any project, from the beginning to end. When to use them, when they can be skipped and what the consequences can be if a process is skipped inappropriately.
Five Enterprise Development Best Practices That EVERY Salesforce Org Can Use
In any environment, non-existent or ad-hoc standards greatly contribute to technical debt. Join us as we explain why Salesforce's multi-tenant architecture and its platform and governor limits make managing technical debt in the App Cloud so critical. You'll discover five best-practices that can make an immediate impact on the maintainability and scalability of your org.
Five Enterprise Best Practices That EVERY Salesforce Org Can Use (DF15 Session)
The document discusses five best practices for Salesforce development that every org should adopt: 1) adopting a standard coding style, 2) following trigger best practices, 3) following unit test best practices, 4) adopting a version of separation of concerns, and 5) adopting specific naming conventions. For each best practice, the document outlines the key benefits, common adoption challenges, and how to execute. It emphasizes establishing governance through documentation, code reviews, and team effort to successfully implement best practices.
Similar to Techdaysnl - code review features in tfs vnext (20)
SPCA2013 - Test-driven Development with SharePoint 2013 and Visual Studio
SPCA2013 - Test-driven Development with SharePoint 2013 and Visual Studio
Case Study: Time Warner Cable's Formula for Maximizing Adobe Experience Manager
Case Study: Time Warner Cable's Formula for Maximizing Adobe Experience Manager
Portal Deployment Best Practices | IBM Portal Excellence Conference 2009
Portal Deployment Best Practices | IBM Portal Excellence Conference 2009
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Parasoft .TEST, Write better C# Code Using Data Flow Analysis
Successful Software Projects - What you need to consider
Successful Software Projects - What you need to consider
Five Enterprise Development Best Practices That EVERY Salesforce Org Can Use
Five Enterprise Development Best Practices That EVERY Salesforce Org Can Use
Five Enterprise Best Practices That EVERY Salesforce Org Can Use (DF15 Session)
Five Enterprise Best Practices That EVERY Salesforce Org Can Use (DF15 Session)
More from Jesse Houwing
Trusting the Unknown
Continuous Integration, Continuous Delivery, workflow automation, more and more tools rely on a vibrant marketplace to share extensions that add new functionality to the systems.
Unfortunately, this means you’re putting trust into a LOT of different people and many of these extensions are built by professionals and enthusiasts in their limited spare time.
GitHub has such a marketplace for Actions and Azure DevOps one for Pipelines. But how do you know whether you can trust these extensions, how do you stay up to date and if you’re building these extensions yourself, how do you keep them secure and your users on the latest version?
Jesse takes us through some of the best practices from the perspective of an extension author, user as well as the administrator of the system that loads these extensions.
Azure DevOps Extension Tools
Quick introduction into common patterns for the Azure DevOps Extension Tools. How to use them, where to find more information.
Ohh shit git
Ohh shit git! - Even I regularly exclaim this when trying to get work done with Git and Visual Studio. Many people coming from TFVC and other systems regularly bump into some crazy situations and need to figure out how to get back to usable state. Updated version presented at Bregler: https://www.bergler.nl/event/werken-git-praktijk/
Ohh sh*t git
Ohh shit git! - Even I regularly exclaim this when trying to get work done with Git and Visual Studio. Many people coming from TFVC and other systems regularly bump into some crazy situations and need to figure out how to get back to usable state.
Dress up my VSTS
Visual Studio Team Services has a load of extensions available for it in the marketplace. During this 45 minute talk we went through as many of them as wel could and looked at some of the best and the weirdest ones out there.
The new way to extend VSTS Build and Release
Extending the new Build and Release features of Visual Studio Team Services (and TFS) helps you turn your scripts into easily re-usable build steps. There are a number of options, from simple scripts to complete custom tasks built using C#, PowerShell or Typescript. We’ll walk through the options and will pros and cons each and quickly walk through the process of building and releasing a custom task to the Visual Studio Marketplace.
When scrum goes bad
Scrum is simple. It has 11 elements. 5 Events, 3 Roles and 3 Artifacts. But even though Scrum is simple, it is hard. Hard to do right. Daily scrum’s only on Tuesdays? A Sprint Demo? The team asking for approval from their Product Owner at Sprint Review… These are only a few of the ways scrum can get corrupted. Let’s scan out collective Scrum hard dive and run chkdks /f on it to get rid of some of the bad sectors, rebuild some of the indexes and resolve the lost files.
Scrum workshop for Project Managers
A 2 hour workshop for traditional Project Managers to see how they'd respond and how one would if they were doing scrum. It's a little old (over 2 years ago), but still valuable enough to share.
Let's get agile: An Agile Talk About Agile
An agile talk about Agile (Avanade Inspire Conference 2013).
We held an agile talk/workshop on the subject of agile, the presentation doesn't contain much in terms of details, but it was used as a template for the presentation format.
We started out with 3 epics, the main subjects that had been requested prior to the conference. After detailing the backlog with the people in the room we did a game to show how self-organisation might work and how action leads to more result than thinking the solution through.
While the game was ongoing my co-presenter went through the questions to build a backlog.
After each 15 minutes the audience had the chance to say that they had received enough value for the epic and thus wanted to move to a new subject or that they wanted to know more.
After each 15 minutes the audience had the opportunity to add new questions and anecdotes to the backlog.
We concluded the talk after 3 scrums with a short review, summary and retrospective.
The format was very well received by the group.
Techdays 2012 - Better code through reviews and tools
Techday 2013 Presentation I did with Thomas Huijer.
Growing great (agile) teams
This document discusses great agile teams and is authored by Jesse Houwing, a senior consultant. It emphasizes that agile teams need direction, vision, and the right tools to drive the creative process. The document provides contact information for the author and lists additional interesting reads and open space discussion topics about agile development practices.
More from Jesse Houwing (11)
Techdays 2012 - Better code through reviews and tools
Techdays 2012 - Better code through reviews and tools
Recently uploaded
Essentials of Automations: The Art of Triggers and Actions in FME
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Things to Consider When Choosing a Website Developer for your Website | FODUU
Choosing the right website developer is crucial for your business. This article covers essential factors to consider, including experience, portfolio, technical skills, communication, pricing, reputation & reviews, cost and budget considerations and post-launch support. Make an informed decision to ensure your website meets your business goals.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Retrieval-Augmented Generation (RAG) systems with open-source and custom AI models is a complex task. This talk explores the challenges in productionizing RAG systems, including retrieval performance, response synthesis, and evaluation. We’ll discuss how to leverage open-source models like text embeddings, language models, and custom fine-tuned models to enhance RAG performance. Additionally, we’ll cover how BentoML can help orchestrate and scale these AI components efficiently, ensuring seamless deployment and management of RAG systems in the cloud.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Full-RAG: A modern architecture for hyper-personalization
Mike Del Balso, CEO & Co-Founder at Tecton, presents "Full RAG," a novel approach to AI recommendation systems, aiming to push beyond the limitations of traditional models through a deep integration of contextual insights and real-time data, leveraging the Retrieval-Augmented Generation architecture. This talk will outline Full RAG's potential to significantly enhance personalization, address engineering challenges such as data management and model training, and introduce data enrichment with reranking as a key solution. Attendees will gain crucial insights into the importance of hyperpersonalization in AI, the capabilities of Full RAG for advanced personalization, and strategies for managing complex data integrations for deploying cutting-edge AI solutions.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Recently uploaded (20)
Essentials of Automations: The Art of Triggers and Actions in FME
Essentials of Automations: The Art of Triggers and Actions in FME
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Things to Consider When Choosing a Website Developer for your Website | FODUU
Things to Consider When Choosing a Website Developer for your Website | FODUU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Infrastructure Challenges in Scaling RAG with Custom AI models
Infrastructure Challenges in Scaling RAG with Custom AI models
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Full-RAG: A modern architecture for hyper-personalization
Full-RAG: A modern architecture for hyper-personalization
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Techdaysnl - code review features in tfs vnext
- 9. C# C#
- 11. Spot simple
- 12. Uhm?!
- 13. Others with the right tools
- 14. All to… prevent issues later
- 15. Tool based, when? Process demands it In some organizations all review comments must be stored for traceability C# Geographical / timing constraints Sometimes there are reasons why you can’t sit together Involving subject matter experts Sometimes you need someone from outside the team, a finance or a math expert, for example, to verify your code
- 17. Pre-check in Make the change Shelve the code Receive Review Unshelve and check in
- 18. Post-check in Make the change Check in your code Receive Review Apply fix
- 20. Tools Team Review http://teamreview.codeplex.com TFS Code Review Workflow http://tfscodereviewflow.codeplex.com/
- 22. Scenarios Supports Pre- and Post-check in reviews of change sets
- 23. How does it work Scenario is technically the same Requires Team Foundation Server Cannot be changed
- 24. Workarounds To allow arbitrary code reviews or audits To allow review of pre-release code
- 25. Demo
- 27. Export work item types Update your process template Or apply directly to an existing project http://msdn.microsoft.com/en-us/library/ms243883.aspx
- 28. C# C#