Delivering software - process and infrastructure
•Download as PPTX, PDF•
0 likes•423 views
This document discusses processes and infrastructure for delivering software. It describes a development process of developing, testing, and fixing errors before release. It then outlines roles in the process like developers, business, and operations. The document details a delivery process with commit and acceptance test stages to increase confidence in a build's readiness for production through faster feedback. It advocates for continuous delivery using tools like source control, continuous integration, and configuration management.
Report
Share
Report
Share
Recommended
Build your QA Pipeline using Serenity , Selenium WebDriver , Rest Assured and...
Learn how to build your QA Pipeline using Serenity, Selenium WebDriver , Rest Assured, Jenkins Pipeline and Ocean Blue
Cloud for Agile Testing - Burak Koyuncu
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.
Continuous integration testing fundamentals
This document discusses fundamentals of continuous integration testing. It explains that continuous integration aims to minimize integration time through frequent code commits, builds, tests and deployments. This allows bugs to be identified and fixed regularly to avoid delays. The document also describes various types of continuous testing like unit testing, functional testing, regression testing, performance testing, load testing, scalability testing and advantages of each.
Testing with Microsoft Technologies - Kick Off Session
The document provides an overview and agenda for a session on Microsoft testing tools. The session will cover manual testing and test case management using Microsoft Test Manager 2012, automated testing using coded UI tests in Visual Studio 2012, web performance testing in Visual Studio 2012, cloud-based load testing in Visual Studio 2013, application lifecycle management using Visual Studio Online 2013, and working with Team Foundation Server 2012.
DevOps Testing | Continuous Testing In DevOps | DevOps Tutorial | DevOps Trai...
***** DevOps Masters Program : https://www.edureka.co/masters-progra... *****
This tutorial on DevOps testing will help you understand how Continuous Testing takes place in the DevOps lifecycle and which tools are used for the same. The following topics have been covered in this video:
1. What Is Continuous Testing?
2. Various Testing Types
3. Tools Used For Continuous Testing
4. Demo: Maven, Selenium, TestNG & Jenkins Integration
CI-CD and DevOps with Ruby
DevOps is a set of practices aimed at reducing the time between committing code changes and deploying to production while ensuring high quality. It involves treating operations teams as first-class citizens in requirements, making developers responsible for incidents, enforcing consistent deployment processes, using continuous delivery and infrastructure as code. The DevOps lifecycle integrates requirements, development, build, testing, deployment and execution with tools for continuous integration, delivery and monitoring. Adopting CI/CD and DevOps can accelerate time to market, build the right products through frequent releases, improve productivity, deliver reliable releases, improve quality and increase customer satisfaction. A roadmap for DevOps includes improving transparency, implementing CI/CD practices, improving communication between teams, and changing
Quickstart for continuous integration
This document provides an introduction to continuous integration (CI), including its objectives, benefits, and how to get started with CI. CI aims to integrate components, software, and infrastructure through short, frequent integration cycles to reduce integration problems and improve productivity. Benefits include anticipating risks early, reducing errors, providing fast feedback, lowering release stress, and enabling collaboration. The document recommends choosing build and scripting tools, using a configuration management system, selecting a CI tool like Jenkins, and setting up a CI "playground" for testing. It provides examples of configuring projects and jobs in Jenkins along with collecting build statistics, reports, and notifications.
Meeting CI/CD Requirements: Key Factors in Test Automation We Must Consider -...
** Full webinar recording: **
Automated tests are a key component of continuous integration (CI) pipelines. They provide confidence that with newly added check-ins, the build will still work as expected. In some cases, the automated tests have the additional role of gating deployments upon failure.
With such a critical responsibility, it's important that automated tests are developed to meet the needs of continuous integration.
In this webinar, Angie Jones (Applitools) and Jessica Deen (Microsoft) discussed key factors that should be considered when writing tests that will run as part of CI.
Angie and Jessica will also show a live demo of integrating frontend tests to your pipeline within an Azure DevOps build -- so we can see all those theories come to life.
Recommended
Build your QA Pipeline using Serenity , Selenium WebDriver , Rest Assured and...
Learn how to build your QA Pipeline using Serenity, Selenium WebDriver , Rest Assured, Jenkins Pipeline and Ocean Blue
Cloud for Agile Testing - Burak Koyuncu
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.
Continuous integration testing fundamentals
This document discusses fundamentals of continuous integration testing. It explains that continuous integration aims to minimize integration time through frequent code commits, builds, tests and deployments. This allows bugs to be identified and fixed regularly to avoid delays. The document also describes various types of continuous testing like unit testing, functional testing, regression testing, performance testing, load testing, scalability testing and advantages of each.
Testing with Microsoft Technologies - Kick Off Session
The document provides an overview and agenda for a session on Microsoft testing tools. The session will cover manual testing and test case management using Microsoft Test Manager 2012, automated testing using coded UI tests in Visual Studio 2012, web performance testing in Visual Studio 2012, cloud-based load testing in Visual Studio 2013, application lifecycle management using Visual Studio Online 2013, and working with Team Foundation Server 2012.
DevOps Testing | Continuous Testing In DevOps | DevOps Tutorial | DevOps Trai...
***** DevOps Masters Program : https://www.edureka.co/masters-progra... *****
This tutorial on DevOps testing will help you understand how Continuous Testing takes place in the DevOps lifecycle and which tools are used for the same. The following topics have been covered in this video:
1. What Is Continuous Testing?
2. Various Testing Types
3. Tools Used For Continuous Testing
4. Demo: Maven, Selenium, TestNG & Jenkins Integration
CI-CD and DevOps with Ruby
DevOps is a set of practices aimed at reducing the time between committing code changes and deploying to production while ensuring high quality. It involves treating operations teams as first-class citizens in requirements, making developers responsible for incidents, enforcing consistent deployment processes, using continuous delivery and infrastructure as code. The DevOps lifecycle integrates requirements, development, build, testing, deployment and execution with tools for continuous integration, delivery and monitoring. Adopting CI/CD and DevOps can accelerate time to market, build the right products through frequent releases, improve productivity, deliver reliable releases, improve quality and increase customer satisfaction. A roadmap for DevOps includes improving transparency, implementing CI/CD practices, improving communication between teams, and changing
Quickstart for continuous integration
This document provides an introduction to continuous integration (CI), including its objectives, benefits, and how to get started with CI. CI aims to integrate components, software, and infrastructure through short, frequent integration cycles to reduce integration problems and improve productivity. Benefits include anticipating risks early, reducing errors, providing fast feedback, lowering release stress, and enabling collaboration. The document recommends choosing build and scripting tools, using a configuration management system, selecting a CI tool like Jenkins, and setting up a CI "playground" for testing. It provides examples of configuring projects and jobs in Jenkins along with collecting build statistics, reports, and notifications.
Meeting CI/CD Requirements: Key Factors in Test Automation We Must Consider -...
** Full webinar recording: **
Automated tests are a key component of continuous integration (CI) pipelines. They provide confidence that with newly added check-ins, the build will still work as expected. In some cases, the automated tests have the additional role of gating deployments upon failure.
With such a critical responsibility, it's important that automated tests are developed to meet the needs of continuous integration.
In this webinar, Angie Jones (Applitools) and Jessica Deen (Microsoft) discussed key factors that should be considered when writing tests that will run as part of CI.
Angie and Jessica will also show a live demo of integrating frontend tests to your pipeline within an Azure DevOps build -- so we can see all those theories come to life.
What is Continuous Integration and Continuous Delivery
Continuous integration and Continuous Delivery are the processes, where your development team involves frequent code changes that are pushed in the main branch while ensuring that it does not impact any changes made by developers working parallelly. The aim of it is to reduce the chance of defects and conflicts during the integration of the complete project. Let’s take a deep dive and learn more about the fundamentals of Continuous Integration and Continuous Delivery.
Software testing
Our completely developed process for independent software testing services ensure international standard of delivery, on-time accomplishment, and the minimum possible cost investment.
Continuous Integration
Continuous integration (CI) is a software development practice where developers integrate code into a shared mainline several times a day, triggering automated builds and tests to detect issues early. At Valsatech, CI is implemented using Jenkins and runs tests across a pool of test beds in parallel to validate code changes with every commit, improving quality and reducing risk. The CI system supports both automated unit and end-to-end integration testing across GUI, services, and APIs for web, native, and mobile applications. Comprehensive reports are generated for each build.
Why should you consider outsourcing your software testing to independent soft...
Independent software testing services are testing professionals whose sole purpose is software testing. They are not related to the product development team. This article explains how outsourcing your software testing to an independent software testing company benefits your business. https://bit.ly/2ZsW6GK
Devops and the New Culture
Talk about:
Software evolution
Continuous delivery
Design
Architecture
SOA
Fault Tolerance
Docker
Continuos Delivery
Continuous delivery is a software development practice where software can be released to production at any time. The key aspects are keeping software deployable over working on new features, allowing anyone to get automated feedback on production readiness from changes, and performing push-button deployments of any version to any environment on demand. This reduces risks and allows for faster user feedback and believable progress. At MagmaLabs, they implement continuous delivery through feature branches, pull requests, review apps, a protected master branch, and CI/CD pipelines to deploy to staging and production. Lessons learned include advanced sprint planning, trustable tests, review apps using staging data, no development branches, feature switches instead of long PRs, and hotfix branches
Continuous integration practices to improve the software quality
This document discusses practices for continuous integration to improve software quality. It recommends analyzing workflows to find areas for automation. It also advocates for self-service builds and push-button deployments across environments. The document outlines patterns like committing code daily, enforcing code quality rules, and stopping broken builds quickly. It notes how continuous integration supports agile methods through daily feedback, using reports to continuously improve processes and quality over iterations.
Monitoring at the Speed of DevOps
Manual Monitoring Slows Deployment and Introduces Risk
How often do you update your applications?
“We deploy multiple times per day” seems to be the new badge of honor for DevOps.
But what you don’t often hear about are the problems caused by process acceleration as a result of continuous integration and continuous deployment (CI/CD).
Rapid introduction of performance problems and errors
Rapid introduction of new endpoints causing monitoring issues
Lengthy root cause analysis as number of services expand
When implementing CI/CD, ANY manual intervention slows down the entire pipeline. You can’t achieve complete CI/CD without automating your monitoring processes (just like you did for integration, testing, and deployment).
Shift left - find defects earlier through automated test and deployment
Do you know how much time it takes or how that translates into dollars lost every time you fix a defect in development, QA, or Production? The cost of application failures or errors increases exponentially the further into the delivery pipeline they are when found. If application defects are discovered by end users in Production, or errors cause a Production outage, the cost can be thousands per second, in addition to the intangible loss of reputation.
So how do you begin to identify defects earlier in software development and prevent them from becoming major, costly errors later on? Join Al Wagner, IBM Technical Evangelist, as he discusses how to "shift left" and;
Incorporate service virtualization and automated testing into development for a more thorough and accurate representation of application quality
Integrate deployment automation with continuous testing to remove wait times on application promotion
Adopt best practices that have proven successful for IBM customers who are currently shifting left
Continuous testing in agile projects 2015
This document discusses continuous testing in an agile environment. It defines continuous testing as testing throughout the development process to identify bugs early. It explains that continuous testing helps control side effects, avoid defects, support multiple environments, get fast results, anticipate risks, and create reliable processes. The document provides an overview of how continuous testing works, including test environments, data management, automatic deployment, and test automation. It also discusses creating a continuous testing project, the agile test process, and how to implement effective continuous testing to improve quality and business value.
Effective Software Testing
Software testing involves investigating a software product or service to find any issues that could compromise the system. The goals of testing are to find errors, ensure reliability and operability, satisfy customer expectations, and deliver a high-quality product. There are different types of testing, including functional tests like unit, integration, and system testing, and non-functional tests for performance, security, and more. A successful test covers all code paths, eventualities, and gathers metrics to track bugs.
Continuous delivery mobile application development
This document discusses continuous delivery for mobile application development. It describes how a team previously spent 9 months developing a mobile app before releasing it live, with another 2 months spent fixing bugs. The document then outlines a continuous delivery process involving continuous integration, implementing a full production pipeline with testing at each stage, configuration management, and enabling push button releases. This approach aims to minimize lead time from idea to live release by keeping software always production ready and releasing tied to business needs rather than IT constraints.
Top 5 Features To Look for in a Codeless Automation Solution -- Presentation ...
** Webinar recording: https://youtu.be/r_gzKJUK_AY **
Watch this on-demand session to discover what are the must-have features of codeless automation solutions.
Manual testing is necessary for certain types and modes of testing -- but its inability to properly and quickly scale up creates major setbacks and bottlenecks for companies.
So what's the answer?
We see organizations turning their attention and resources to codeless automation solutions in the hopes of solving the issues of speed, coverage, and maintenance -- but how do you choose a solution that is right for your team?
In this session, we dived into the 5 key features you should look for in a codeless automation solution, discussed how each of those features helps solve different testing challenges, and demonstrated how those features work.
Integrate Visual AI Into Your Appium Scripts in Minutes
The document discusses challenges with traditional automated testing frameworks, such as tests being time-consuming to author and maintain, prone to flakiness, and unable to detect modern app defects. It introduces a visual AI platform that augments test frameworks with computer vision capabilities, allowing tests to be created faster with fewer brittle locators and providing more efficient and effective testing.
Jenkins Test Automation with codeBeamer ALM
Testing is a vital part of software development, since it is about finding the software bugs. You can choose from automated and manual testing. Automated testing is good for large projects with many systems users, while manual testing is good for smaller projects or for companies with insufficient budget.
You can also run Continuous testing. The purpose of Continuous testing and continuous integration is to enable continuous delivery, the end goal of which is to accelerate the delivery of high quality software.
Automation is essential for Continuous Testing but Automated Testing is not the same as Continuous Testing.
Try Jenkins Test Automation with codeBeamer ALM. Jenkins is an open source continuous integration tool written in Java. Jenkins provides continuous integration services for software development.
Brave New World - A wider perspective of our opportunities
The world has changed. We feel it in the work environment. We see it in the numbers. We smell it in the questions. Much that once was, is lost, for few remember it, even less still use it. In the name of agility and lean processes, we have turned a blind eye to quality, favouring quick execution over customer delight. And some things that should not have been forgotten were lost.
Join Jay Rao and Vishal Anand to explore the new world of “agile delivery”. Understand the myths vs the real picture, the anti-patterns to watch out for and how you can look forward to understanding new measurements for delivery, and various functions within – from architecture to deployment – and where each of us has opportunities that align with common sense and outcomes
Keeping Your Continuous Test Automation Continuously Valuable
When executing test automation at scale and continuously the value tends to decline over time, the team should follow recommended practices to keep their tests with high value.
Getting the value from your test automation is fundamental for fast feedback, risk reduction and return on investment from your testing activities. Getting the value from your test automation is fundamental for fast feedback, risk reduction and return on investment from your testing activities.
Once developing the test scenarios, teams cannot stop monitoring and ensuring that their tests continuously bring value, are not flaky, and can support the latest functionalities in your web and mobile apps. Teams often “forget” about their tests once they have been developed and integrated into the CI pipeline regardless of the value they bring.
Key Takeaways:
-How to make smart decisions regarding which test scenarios to automate?
-What are the criteria for a test to get included in the CI and continuous testing pipeline?
-How to continuously maintain the tests and optimize your suite so it continues to bring value?
-See a live demo of smart reporting and analytics that can serve as a monitoring and test maintenance tool.
Continuous Integration
This whitepaper explains best practice methodology for Continuous Integration and the benefits it delivers.
CI allows Computaris to deliver outstanding results – faster. Computaris has an excellent track record of delivering successful projects. Customers come to Computaris for both new projects and to seek counsel on existing projects expecting swift turnaround times combined with excellent quality.
SPCA2013 - Taking advantage of Visual Studio to develop Apps for SharePoint
This document outlines a continuous delivery model for developing and deploying applications. It includes steps for defining requirements, developing working software, implementing feedback, monitoring performance, and adapting over time. A diagram shows how developers check in code changes, automated builds are deployed to test environments, tests are run, issues are fixed, and corrected builds are deployed to production. Testing times are reduced through automation of deployments, full traceability of changes, and management of lifecycle artifacts.
Assessment 2011
The document discusses the second stage of assessment which is determining acceptable evidence of student learning, such as how teachers will know if students have achieved desired results and standards. It explains that teachers should think about what types of assessment evidence is needed to show students have achieved the goals outlined in stage 1. The document also provides examples of how students can demonstrate their understanding through explanation, interpretation, application, perspective, empathy, and self-knowledge.
More Related Content
What's hot
What is Continuous Integration and Continuous Delivery
Continuous integration and Continuous Delivery are the processes, where your development team involves frequent code changes that are pushed in the main branch while ensuring that it does not impact any changes made by developers working parallelly. The aim of it is to reduce the chance of defects and conflicts during the integration of the complete project. Let’s take a deep dive and learn more about the fundamentals of Continuous Integration and Continuous Delivery.
Software testing
Our completely developed process for independent software testing services ensure international standard of delivery, on-time accomplishment, and the minimum possible cost investment.
Continuous Integration
Continuous integration (CI) is a software development practice where developers integrate code into a shared mainline several times a day, triggering automated builds and tests to detect issues early. At Valsatech, CI is implemented using Jenkins and runs tests across a pool of test beds in parallel to validate code changes with every commit, improving quality and reducing risk. The CI system supports both automated unit and end-to-end integration testing across GUI, services, and APIs for web, native, and mobile applications. Comprehensive reports are generated for each build.
Why should you consider outsourcing your software testing to independent soft...
Independent software testing services are testing professionals whose sole purpose is software testing. They are not related to the product development team. This article explains how outsourcing your software testing to an independent software testing company benefits your business. https://bit.ly/2ZsW6GK
Devops and the New Culture
Talk about:
Software evolution
Continuous delivery
Design
Architecture
SOA
Fault Tolerance
Docker
Continuos Delivery
Continuous delivery is a software development practice where software can be released to production at any time. The key aspects are keeping software deployable over working on new features, allowing anyone to get automated feedback on production readiness from changes, and performing push-button deployments of any version to any environment on demand. This reduces risks and allows for faster user feedback and believable progress. At MagmaLabs, they implement continuous delivery through feature branches, pull requests, review apps, a protected master branch, and CI/CD pipelines to deploy to staging and production. Lessons learned include advanced sprint planning, trustable tests, review apps using staging data, no development branches, feature switches instead of long PRs, and hotfix branches
Continuous integration practices to improve the software quality
This document discusses practices for continuous integration to improve software quality. It recommends analyzing workflows to find areas for automation. It also advocates for self-service builds and push-button deployments across environments. The document outlines patterns like committing code daily, enforcing code quality rules, and stopping broken builds quickly. It notes how continuous integration supports agile methods through daily feedback, using reports to continuously improve processes and quality over iterations.
Monitoring at the Speed of DevOps
Manual Monitoring Slows Deployment and Introduces Risk
How often do you update your applications?
“We deploy multiple times per day” seems to be the new badge of honor for DevOps.
But what you don’t often hear about are the problems caused by process acceleration as a result of continuous integration and continuous deployment (CI/CD).
Rapid introduction of performance problems and errors
Rapid introduction of new endpoints causing monitoring issues
Lengthy root cause analysis as number of services expand
When implementing CI/CD, ANY manual intervention slows down the entire pipeline. You can’t achieve complete CI/CD without automating your monitoring processes (just like you did for integration, testing, and deployment).
Shift left - find defects earlier through automated test and deployment
Do you know how much time it takes or how that translates into dollars lost every time you fix a defect in development, QA, or Production? The cost of application failures or errors increases exponentially the further into the delivery pipeline they are when found. If application defects are discovered by end users in Production, or errors cause a Production outage, the cost can be thousands per second, in addition to the intangible loss of reputation.
So how do you begin to identify defects earlier in software development and prevent them from becoming major, costly errors later on? Join Al Wagner, IBM Technical Evangelist, as he discusses how to "shift left" and;
Incorporate service virtualization and automated testing into development for a more thorough and accurate representation of application quality
Integrate deployment automation with continuous testing to remove wait times on application promotion
Adopt best practices that have proven successful for IBM customers who are currently shifting left
Continuous testing in agile projects 2015
This document discusses continuous testing in an agile environment. It defines continuous testing as testing throughout the development process to identify bugs early. It explains that continuous testing helps control side effects, avoid defects, support multiple environments, get fast results, anticipate risks, and create reliable processes. The document provides an overview of how continuous testing works, including test environments, data management, automatic deployment, and test automation. It also discusses creating a continuous testing project, the agile test process, and how to implement effective continuous testing to improve quality and business value.
Effective Software Testing
Software testing involves investigating a software product or service to find any issues that could compromise the system. The goals of testing are to find errors, ensure reliability and operability, satisfy customer expectations, and deliver a high-quality product. There are different types of testing, including functional tests like unit, integration, and system testing, and non-functional tests for performance, security, and more. A successful test covers all code paths, eventualities, and gathers metrics to track bugs.
Continuous delivery mobile application development
This document discusses continuous delivery for mobile application development. It describes how a team previously spent 9 months developing a mobile app before releasing it live, with another 2 months spent fixing bugs. The document then outlines a continuous delivery process involving continuous integration, implementing a full production pipeline with testing at each stage, configuration management, and enabling push button releases. This approach aims to minimize lead time from idea to live release by keeping software always production ready and releasing tied to business needs rather than IT constraints.
Top 5 Features To Look for in a Codeless Automation Solution -- Presentation ...
** Webinar recording: https://youtu.be/r_gzKJUK_AY **
Watch this on-demand session to discover what are the must-have features of codeless automation solutions.
Manual testing is necessary for certain types and modes of testing -- but its inability to properly and quickly scale up creates major setbacks and bottlenecks for companies.
So what's the answer?
We see organizations turning their attention and resources to codeless automation solutions in the hopes of solving the issues of speed, coverage, and maintenance -- but how do you choose a solution that is right for your team?
In this session, we dived into the 5 key features you should look for in a codeless automation solution, discussed how each of those features helps solve different testing challenges, and demonstrated how those features work.
Integrate Visual AI Into Your Appium Scripts in Minutes
The document discusses challenges with traditional automated testing frameworks, such as tests being time-consuming to author and maintain, prone to flakiness, and unable to detect modern app defects. It introduces a visual AI platform that augments test frameworks with computer vision capabilities, allowing tests to be created faster with fewer brittle locators and providing more efficient and effective testing.
Jenkins Test Automation with codeBeamer ALM
Testing is a vital part of software development, since it is about finding the software bugs. You can choose from automated and manual testing. Automated testing is good for large projects with many systems users, while manual testing is good for smaller projects or for companies with insufficient budget.
You can also run Continuous testing. The purpose of Continuous testing and continuous integration is to enable continuous delivery, the end goal of which is to accelerate the delivery of high quality software.
Automation is essential for Continuous Testing but Automated Testing is not the same as Continuous Testing.
Try Jenkins Test Automation with codeBeamer ALM. Jenkins is an open source continuous integration tool written in Java. Jenkins provides continuous integration services for software development.
Brave New World - A wider perspective of our opportunities
The world has changed. We feel it in the work environment. We see it in the numbers. We smell it in the questions. Much that once was, is lost, for few remember it, even less still use it. In the name of agility and lean processes, we have turned a blind eye to quality, favouring quick execution over customer delight. And some things that should not have been forgotten were lost.
Join Jay Rao and Vishal Anand to explore the new world of “agile delivery”. Understand the myths vs the real picture, the anti-patterns to watch out for and how you can look forward to understanding new measurements for delivery, and various functions within – from architecture to deployment – and where each of us has opportunities that align with common sense and outcomes
Keeping Your Continuous Test Automation Continuously Valuable
When executing test automation at scale and continuously the value tends to decline over time, the team should follow recommended practices to keep their tests with high value.
Getting the value from your test automation is fundamental for fast feedback, risk reduction and return on investment from your testing activities. Getting the value from your test automation is fundamental for fast feedback, risk reduction and return on investment from your testing activities.
Once developing the test scenarios, teams cannot stop monitoring and ensuring that their tests continuously bring value, are not flaky, and can support the latest functionalities in your web and mobile apps. Teams often “forget” about their tests once they have been developed and integrated into the CI pipeline regardless of the value they bring.
Key Takeaways:
-How to make smart decisions regarding which test scenarios to automate?
-What are the criteria for a test to get included in the CI and continuous testing pipeline?
-How to continuously maintain the tests and optimize your suite so it continues to bring value?
-See a live demo of smart reporting and analytics that can serve as a monitoring and test maintenance tool.
Continuous Integration
This whitepaper explains best practice methodology for Continuous Integration and the benefits it delivers.
CI allows Computaris to deliver outstanding results – faster. Computaris has an excellent track record of delivering successful projects. Customers come to Computaris for both new projects and to seek counsel on existing projects expecting swift turnaround times combined with excellent quality.
SPCA2013 - Taking advantage of Visual Studio to develop Apps for SharePoint
This document outlines a continuous delivery model for developing and deploying applications. It includes steps for defining requirements, developing working software, implementing feedback, monitoring performance, and adapting over time. A diagram shows how developers check in code changes, automated builds are deployed to test environments, tests are run, issues are fixed, and corrected builds are deployed to production. Testing times are reduced through automation of deployments, full traceability of changes, and management of lifecycle artifacts.
What's hot (19)
What is Continuous Integration and Continuous Delivery
What is Continuous Integration and Continuous Delivery
Why should you consider outsourcing your software testing to independent soft...
Why should you consider outsourcing your software testing to independent soft...
Continuous integration practices to improve the software quality
Continuous integration practices to improve the software quality
Shift left - find defects earlier through automated test and deployment
Shift left - find defects earlier through automated test and deployment
Continuous delivery mobile application development
Continuous delivery mobile application development
Top 5 Features To Look for in a Codeless Automation Solution -- Presentation ...
Top 5 Features To Look for in a Codeless Automation Solution -- Presentation ...
Integrate Visual AI Into Your Appium Scripts in Minutes
Integrate Visual AI Into Your Appium Scripts in Minutes
Brave New World - A wider perspective of our opportunities
Brave New World - A wider perspective of our opportunities
Keeping Your Continuous Test Automation Continuously Valuable
Keeping Your Continuous Test Automation Continuously Valuable
SPCA2013 - Taking advantage of Visual Studio to develop Apps for SharePoint
SPCA2013 - Taking advantage of Visual Studio to develop Apps for SharePoint
Viewers also liked
Assessment 2011
The document discusses the second stage of assessment which is determining acceptable evidence of student learning, such as how teachers will know if students have achieved desired results and standards. It explains that teachers should think about what types of assessment evidence is needed to show students have achieved the goals outlined in stage 1. The document also provides examples of how students can demonstrate their understanding through explanation, interpretation, application, perspective, empathy, and self-knowledge.
Raqiya wiki1
This document discusses the growing impact of technology on education and presents strategies for effectively integrating technology into teaching. It notes that while technology has advanced rapidly, education curriculums have not fully embraced technology's importance. The document also addresses challenges like balancing technology with traditional instruction and increasing testing pressures. Additionally, it cautions against overreliance on tools like PowerPoint and advocates using technology visually to engage audiences while addressing complex topics that cannot be overly simplified.
Kesihatan dan kesejahteraan week 1 d
The document discusses different models and theories related to health and wellness. It covers the medical model which focuses on treating disease, injuries, and disabilities with drugs and surgeries. It also mentions the environmental model which considers social and physical factors. A holistic model is described that takes a broader view of health as physiological, mental, emotional, social and spiritual well-being. The dimensions of health and wellness are defined along with several theories of health behavior change.
Theories of the earth's crustal movement powerpoint
The document summarizes theories of continental drift and plate tectonics. In 1915, Alfred Wegener first proposed the theory of continental drift, which states that parts of the Earth's crust slowly drift atop a liquid core. Wegener hypothesized that around 200 million years ago, all the continents were joined together in a supercontinent called Pangaea. Pangaea later broke apart into smaller supercontinents, and by the end of the Cretaceous period the continents had separated into their modern positions. In the 1960s, Harry Hess proposed the theory of seafloor spreading, which provided support for continental drift by showing how ocean floors spread outward from underwater ridges. Plate tectonics expanded on these ideas
Static code analysis
Static code analysis involves using tools to analyze source code for potential issues. It can find bugs, code quality issues, and other problems but is not a replacement for testing. Several experts note that combining static analysis, inspections, and testing leads to better defect removal than only using testing. Common static analysis tools include FxCop, StyleCop, ReSharper, and NDepend. Integrating static analysis into the development process can provide benefits but obstacles like resources and unrealistic expectations must be addressed.
Being able to code does not make you a good developer
Rune Sundling argues in his blog post that being able to code alone does not make someone a good developer. He lists several soft skills that are also important for developers, including taking responsibility, cooperation, communication, listening skills, and considering colleagues, meetings, feedback and one's well-being. Sundling emphasizes that good development requires both technical coding ability as well as soft skills like communication, responsibility and collaboration.
Organizational Structure
This document discusses organizational structure and provides definitions and examples of key concepts. It defines organizational structure as how a group is formed and how communication and authority are channeled. It then discusses the importance of organizational structure for clarifying roles and responsibilities. The document contrasts formal and informal structures and describes centralized and decentralized structures. It also defines organizational charts and discusses types of charts including vertical, horizontal, and circular charts. The key concepts of authority, responsibility, delegation, and accountability are defined.
Viewers also liked (20)
Den ikke tekniske delen av å være konsulent, utvikler og profesjonell
Den ikke tekniske delen av å være konsulent, utvikler og profesjonell
Theories of the earth's crustal movement powerpoint
Theories of the earth's crustal movement powerpoint
Being able to code does not make you a good developer
Being able to code does not make you a good developer
Similar to Delivering software - process and infrastructure
2011 NASA Open Source Summit - Forge.mil
Forge.mil is a collaborative software development platform that aims to overcome siloed development, reduce duplication of effort, and enable cross-program sharing of software and services. It provides application lifecycle management services and tools for collaborative development within a shared, multi-tenant environment for Department of Defense programs and partners. Forge.mil has grown to support over 2700 software releases from various DoD projects across different services since its initial launch in 2009.
Continuous Deployment at Etsy — TimesOpen NYC
Principles and practices in Continuous Deployment at Etsy. Presented by Mike Brittain at TimesOpen (nytimes) on July 22, 2014
Expert Days: The VP R&D Open Seminar: Project Management
All you wanted to know regarding product development, Classic Project Management, SCRUM, Agile, Continuous Deployment, Minimum Viable Product and how to build a winning team
The Big Bang - Upgrading to Banner 8.1
The document summarizes Emporia State University's upgrade of their Banner system from version 8.0 to 8.1. It discusses project planning, scope, business process analysis and testing. The upgrade project took 8 months and involved upgrading various modules including Student, Finance, HR and Advancement to Banner 8.1. It also included upgrading supporting software, hardware infrastructure, and addressing issues encountered during testing and integration. Lessons learned focused on importance of collaboration between functional and technical teams for a successful major release upgrade.
WSO2CON 2024 - Software Engineering for Digital Businesses
WSO2CON 2024 - Software Engineering for Digital Businesses
Cloud continuous integration- A distributed approach using distinct services
In cloud computing services the ability to share and deliver services, scale computing resources and distribute data storage and files requires a deployment process aligned with agility and scalability. The continuous integration can automate process reducing operational effort, improving code quality and reducing time to market. This presentation shows a proposal for distributed continuous integration to use differents cloud computing services, from planning to execution of scenarios.
CI WP Meetup 2013-04-26
This document discusses continuous integration (CI), providing reasons for adopting CI like enabling agile development practices and increasing quality. It defines some key CI concepts and outlines challenges in setting up CI. The document demonstrates setting up a basic CI environment for a WordPress site with a loan calculator plugin in 7 steps: installing a virtual server, services like Jenkins, configuring plugins, test cases, and creating a CI job to run tests and report results. CI is presented as an important practice for enabling continuous delivery in agile development.
Dops 1033 dev-ops_review_final
IBM is reviewing their DevOps roadmap and solutions. They discuss how software delivery is critical for business success but many companies do not leverage it effectively. IBM's DevOps approach uses tools and practices to enable continuous software delivery and reduce time to customer feedback. They have acquired UrbanCode to strengthen their release and deployment capabilities. Future plans include further tool integrations across the development lifecycle.
Zen QA Presentation
ZenQA is a 6 year old company located in Hyderabad, India that provides development and testing services for companies in the US, UK, and Canada. They have 100 experienced .NET developers and test engineers. Their services include .NET development, testing, SharePoint, and Crystal Reports. They have experience testing applications across several domains using tools like IBM Rational, HP Quality Center, and Microsoft Visual Studio. They follow industry standard practices and provide thorough test reports and security testing to identify vulnerabilities. They offer a free 2 week pilot project with 2 test engineers to demonstrate their QA process.
Bje final present-v.1.0
This document summarizes a student project to create an online Beginning Java course. It outlines the project management activities including planning, execution, assessment and closure. It also describes the software implementation activities such as requirements analysis, design, construction, integration, testing and delivery. Key aspects of the project include developing requirements and design specifications, creating test cases, conducting testing, and getting acceptance from the project advisor. The project followed the ISO29110 standard for software life cycle processes and was completed at 100% according to the planned schedule and requirements.
Zibrasoft | Software QA Testing Company Inida
Zibrasoft Technologies has a dedicated team of extremely talented, customer-focused and diligent professionals with a diversified skill set in QA and Testing. We have built expertise around the latest testing tools and technologies. Zibrasoft Technologies is a heading towards with the vision to establish as a global leader in high-end QA and Testing services.Zibrasoft Technologies has experience in working with multiple software platforms of high complexity including complex software systems like Customer Relationship Management (CRM), Web Content Management System (WCMS), ERP and high volume and high traffic consumer website.Zibrasoft Technologies has extended testing team of high caliber in manual and automated testing. Involvement of this extended testing team right through the development lifecycle enables customers to meet the complete requirements of their product. We have experience in providing QA as an extension of our development services or as an independent project.
527759_Resume (5)
The document is a resume for Dipty Jena summarizing their work experience as a Quality Assurance Analyst and Team Lead at Tata Consultancy Services. Some key points:
- Currently working as a Manual(Validation) tester and Team Lead for the Amerisource Bergen Consultancy Services project.
- Over 4 years of experience in roles including developer, tester, and team lead for clients such as Western Union, Indian Bank, and Amerisource Bergen.
- Technical skills include test case writing, manual testing, test execution, defect tracking, and tools like QC, TFS, and PTR. Proficient in languages like Java, JavaScript, SQL.
- Certified in I
XP to Windows 7 with MDT
This is the Windows XP and Office 2003 to Windows 7 and Office 2010 Migration Presentation from the Get On The Bus Tour
Experts Live Europe 2017 - Windows 10 Servicing - the do’s and don'ts
Many companies have already adopted and implemented Windows 10. So far, so good - but the experiences from the field and big threats like WannaCry still demonstrate that many companies have massive trouble in servicing Windows 10. Either some of them simply overengineer the whole process by putting way too much effort into application testing repeatedly or they just give up and let everything happen. In my session, I will show you what my experiences have been. What you should consider and what is just overhead. We will talk about deployment tweaks of Configuration Manager, Application Compatibility, the management process of updates , Upgrade Readiness and how Windows Analytics can help.
SB Support System
The SB Support Application is a new SB application that will be provided as part of the standard installation from version 6.4.0 of SB+ and SB/XA.
In this presentation, we will review the features of this application and discuss how they can be used to improve the support of your SB applications.
Qa engineer dzmitry ananyeu
Dzmitry Ananyeu is a QA engineer with over 4.5 years of experience in testing enterprise document processing systems, information retrieval systems, and online shops. He has expertise in functional testing, test documentation creation, GUI testing, requirements testing, acceptance testing, and test tracking systems like Jira and ClearQuest. Dzmitry has experience testing web applications, databases, and standalone applications including SharePoint-based applications.
Dan Lewis 2014
Dan Lewis has over 10 years of experience in quality assurance testing across several industries. He has expertise in manual testing, defect identification, test management, and test automation. He is certified as an ISTQB Certified Tester at the Foundation Level. Dan has experience using tools like Visual Studio, Microsoft Test Manager, JIRA, and HP Quality Center for testing and defect tracking.
How Meark as an enterprise leverages DSDM?
The presentation covers one of the Agile Methodologies. Dynamic Systems Development Method (DSDM) is a framework based originally around Rapid Application Development (RAD).DSDM recognises that projects are limited by time and resources, and plans accordingly to meet the business needs.
Resume
The document contains a resume for Yamini Patil, who has 2 years of experience as a Software Engineer at Syntel Ltd. where she has worked on testing projects including manual testing, automation testing, integration testing, and regression testing. She is seeking a challenging position in software testing where she can utilize her skills and experience in areas like requirements analysis, test case design, test execution, and defect management.
CV_AmalMandal
This document contains the resume of Amal Mandal summarizing his professional experience as a software engineer with 7 years of experience developing software using technologies like SQL Server, Visual Studio, and SSIS. He has strong skills in software development methodology including development, testing and releasing products on time and to expectations. His experience includes projects for clients like Microsoft, Infosys, Wipro, and Hewlett-Packard.
Similar to Delivering software - process and infrastructure (20)
Expert Days: The VP R&D Open Seminar: Project Management
Expert Days: The VP R&D Open Seminar: Project Management
WSO2CON 2024 - Software Engineering for Digital Businesses
WSO2CON 2024 - Software Engineering for Digital Businesses
Cloud continuous integration- A distributed approach using distinct services
Cloud continuous integration- A distributed approach using distinct services
Experts Live Europe 2017 - Windows 10 Servicing - the do’s and don'ts
Experts Live Europe 2017 - Windows 10 Servicing - the do’s and don'ts
Recently uploaded
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
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
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.
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Climate Impact of Software Testing at Nordic Testing Days
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
UiPath Test Automation using UiPath Test Suite series, part 6
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
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.
Mind map of terminologies used in context of Generative AI
Mind map of common terms used in context of Generative AI.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
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.
Recently uploaded (20)
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
GraphSummit Singapore | Graphing Success: Revolutionising Organisational Stru...
Climate Impact of Software Testing at Nordic Testing Days
Climate Impact of Software Testing at Nordic Testing Days
UiPath Test Automation using UiPath Test Suite series, part 6
UiPath Test Automation using UiPath Test Suite series, part 6
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
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
Mind map of terminologies used in context of Generative AI
Mind map of terminologies used in context of Generative AI
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
GraphSummit Singapore | Neo4j Product Vision & Roadmap - Q2 2024
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Delivering software - process and infrastructure
- 1. Delivering software - Process and infrastructure demands NNUG 26.10.2010 , 26.10.2010Delivering software - Process and infrastructure demands Page 1
- 2. Delivering software - Process and infrastructure demands Page 2 , 26.10.2010 Rune Sundling Itera Consulting (tidligere Objectware) Twitter: @runesundling Blog: http://runesundling.blogspot.com
- 3. Delivering software - Process and infrastructure demands Page 3 , 26.10.2010 What do we want to achieve?
- 4. Delivering software - Process and infrastructure demands Page 4 , 26.10.2010 The development process Develop Test Fix errors Release Ideas Planning/ Requirements
- 5. Delivering software - Process and infrastructure demands Page 5 , 26.10.2010 Roles Developers Business Operations Testers
- 6. Delivering software - Process and infrastructure demands Page 6 , 26.10.2010 Delivery process Commit stage Compile Unit test Analysis Acceptance test stage User acceptance testing Capacity testing Production Environments become more production-like Increasing confidence in build’s production readiness Faster feedback
- 7. Delivering software - Process and infrastructure demands Page 7 , 26.10.2010 Delivery process
- 8. Delivering software - Process and infrastructure demands Page 8 , 26.10.2010 Delivery process Commit stage Compile Commit tests Assemble Code analysis Acceptance stage Configure environments Deploy binaries Smoke test Acceptance tests Production Configure environments Deploy binaries Smoke test UAT Configure environments Deploy binaries Smoke test Capacity testing Configure environment Deploy binaries Smoke test Run capacity tests Source code Env & app config Env & app config Version control Artifact repository Developers Testers Operations See code metrics and test failures Self-service deployments Perform push-button releases reports binaries metadata binaries reports metadata binaries reports metadata
- 9. Delivering software - Process and infrastructure demands Page 9 , 26.10.2010 Continuous delivery - Resharper nightly build
- 10. • Source control • Continuous integration • Configuration management • Testing • Data management • Build and deployment scripting • Continuous delivery Delivering software - Process and infrastructure demands Page 10 , 26.10.2010 Related topics
- 11. • Continuous Delivery • DevOps movement Delivering software - Process and infrastructure demands Page 11 , 26.10.2010 References and recommended reading