Implementing Azure DevOps With Your Testing Project Are you challenged with different teams working on different platforms making it difficult to get insight into another team’s work? Is your team seeking ways to automate the code deployments so you can spend more time developing new features and writing more tests, and spend less time deploying and running manual tests? RTTS, a Microsoft Gold DevOps Partner, will take you through solving these challenges with Azure DevOps. Tuesday, June 16th 2020 @11am ET Session Overview ------------------------------------ During the webinar, we will walk you through the following process of utilizing Azure DevOps: - The challenges that inspired the Azure DevOps solution that you may experience as well - The strategy for implementing Azure Devops - Solutions in our every day processes to increase our times efficiency and save time - A demo of an Azure DevOps environment for testing teams The see a recording of the webinar, please visit: https://www.youtube.com/watch?v=2vIic3wxaS4 To learn more about RTTS, please visit: https://www.rttsweb.com

1. Liz Levine
Marketing Manager
Jan Tacbianan
Senior Test Engineer
Implementing Azure DevOps
with Your Testing Project

2. The premier pure-play
automated QA & testing experts
providing innovative Test Automation solutions
to 700+ companies since 1996

3. Facts
Founded:
1996 (24th anniversary)
Location:
New York City (HQ)
Customer profile:
• Fortune 500 & mid-size
• 700+ customers
Strategic Partners:
IBM, Microsoft, Oracle,
Teradata, Cloudera,
HortonWorks, MongoDB,
SAP, Micro Focus
Other Software
Supported
QuerySurge, Selenium,
Appium, CitraTest,
Postman, Smart Bear,
JMeter, others
RTTS is the premier pure-play QA & Testing firm
that specializes in Test Automation

4. Agenda
 Summary Agile & DevOps/DevSecOps
 Introduction of Azure DevOps
 Azure DevOps and Testing

5. Does your software project check any of these boxes?
 Develop a digital product: software, web applications, websites, ecommerce,
digital marketing
 Have a team composed of stakeholders, business product owners,
developers, QA, and IT operations
 Have different members of the team are utilizing different platforms to track
and perform their tasks and responsibilities
 Difficulty measuring progress across teams
 Utilize a linear approach to software development
If so… Your team may benefit from switching to…

6. Agile & DevOps Culture

7. What is Agile?
 Iterative approach to software development
 Taking ideas and bringing them to market in smaller, digestible increments quickly
and efficiently.
 Responding and adapting to change
 Delivering value to the consumers
 Re-evaluating requirements, plans, and results.
 Constantly learning

8. Manifesto for Agile Software Development
We are uncovering better ways of developing software by
doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value
the items on the left more.
*From https://agilemanifesto.org

9. What is DevOps?
 Methodologies, Practices, Philosophies
 Bringing development and operations together
 DevOps isn’t a “standard”, “process”, or a “tool”
 Notes:
 Development and Operations
 Not just: Developers or Operators
 DevOps includes people, processes, tools, and products.
 Moving to a DevOps “culture” may also mean changing what we see as the
deliverable.

10. What is DevSecOps?
 Bringing DevOps and SecOps together
 Integrating security earlier into the application life cycle process.

11. What role does QA play in a DevOps/DevSecOps Culture?
 Quality still plays a role in an Agile and DevOps culture.
 But it may be different than how many are used to.
 Changes to approach:
 Acceptance Test Driven Development
 Continuous Testing
 Automation
 A robust testing plan is essential to any agile project

12. Using an Agile or DevOps oriented tool
doesn’t mean you’re running an agile
project or practicing a DevOps culture…
But it does certainly makes it easier!

14. Why Microsoft Azure DevOps?
 Cloud Based Platform
 Option to host on-premise (Azure DevOps Server)
 Included with Visual Studio Subscription
 Integrates with Azure Active Directory / Microsoft 365
 Includes all major components under one platform
 Works for all software development projects, regardless of platform, language, or
distribution medium.
 Supports integrations and plugins for many existing tools and products

15. Components of Azure DevOps
 Boards
 Repos
 Pipelines
 Test Plans
 Artifacts

16. Azure Boards
 Work Item Management
 Project Planning & Management
 Boards
 Backlogs
 Sprints
 Queries
 Dashboards

17. Azure Repos
 Version Control Tools
 Git Support
 Unlimited Repos
 Standard Git Implementation
 Branch Policies
 Pull Requests
 Team Foundation Version Control
 Centralized version control

18. Azure Pipelines
 Tools for the automation of builds, tests, and deployments
 Continuous integration and continuous delivery
 Supports most languages and application/product types
 Integrates with Azure Repos and other version control
systems
 Supports various deployment targets

19. Azure Test Plans
 Test Management Platform
 Manual Testing
 User Acceptance Testing
 Exploratory Testing
 Load Testing

20. Azure Artifacts
 Artifact Management
 Feeds
 NuGet
 Npm
 Maven
 Use with develop and CI/CD Pipelines

21. Interoperability Between Azure DevOps Components
 Pipelines/Builds driven by version control
 Branches created from work items
 Releases driven by artifacts
 Bugs created by failed tests
 Work items progressed by passed tests
 Dashboards are driven by all components
 All components are designed to work together

22. With DevOps, our infrastructure is also a deliverable.

23. Infrastructure as Code
 All components of a product can be a deliverable.
 Application Code (Application)
 Testing Code (Tests)
 Infrastructure Code (Environment)
 Deployment Code (Deployment)
 A new environment or project fork should be quick and seamless
to stand up

24. Integrating Testing into your DevOps or CI/CD Workflow

25. Automated Testing
 UI Testing
 Selenium Scripts
 Appium Scripts
 API/Web Service Testing
 Postman/Newman
 MS Test

26. Regression Testing
 Deployment Automation
 Verify Environment Stability
 Application Integration Tests
 Infrastructure Tests
 Resource Allocation
 Policy Tests

27. Scheduled Testing
 Scheduled Test Builds/Artifacts
 Security Tests
 Baseline Tests
 Snapshots of current environment

28. Security Tests
 Security Test Scripts
 Authentication Validation
 Authorization Policies
 Throttling

29. Data Testing & Validation
 End-to-End test automation
 Backend Validation
 Data Migration Validation
 Data Quality

30. Dependency Tests
 Third-party/vendor dependency tests
 Health Checks
 Regression Tests

31. Takeaways
 Collaboration and constant adjustment provides additional value to business and
consumers
 Utilizing an Agile and DevOps approach increases transparency across different
teams
 When projects are being developed and delivered faster and more often, the role
of testing and quality assurance plays an important role in ensuring a quality product.
 Not everything mentioned in the presentation must happen at the same time.

32. RTTS’ Azure DevOps webinar on YouTube
https://www.youtube.com/watch?v=2vIic3wxaS4
RTTS web site
www.rttsweb.com
QuerySurge web site
www.QuerySurge.com