This document summarizes a presentation about babysitting your ORM with a custom TFS build. The presentation discusses integrating ORM performance analysis into your ALM process using TFS and a profiling tool. It reviews ORMs and CI/TFS, demonstrates why measuring an ORM's behavior is important using examples, and shows a demo of writing tests, committing code through a gated check-in, and viewing profiling results on individual tests to detect issues like N+1 queries. The goal is to apply simple ideas and best practices to gain real, measurable ROI from monitoring ORM performance in your builds and tests.
1.microsoft visual studio 2010 test managerAshwin Jujgar
The document discusses Microsoft Visual Studio 2010 and Test Manager. It provides an overview of Visual Studio Team System 2010 and its tools for software development, testing, and management. It also describes the capabilities of Microsoft Test Manager for test planning, case management, execution and defect tracking. Finally, it demonstrates some of these capabilities through a test planning and execution demo.
This document discusses challenges with automated unit and integration testing involving databases. It presents RoundhousE and NDbUnit as tools that help address these challenges by managing database schema changes and ensuring data is in a known state before tests. Examples of how these tools work would be helpful to understand how they automate testing of database-related code.
testing is an important part of programming and software engineering. In this slide, I share insight on how to get started with writing tests in Django
These slides provide the high-level results of our comparison of FxCop and the Coverity platform. We used a third party codebase of approx. 100k lines of code and analyzed it using the "fxcop" from Visual Studio 2013 and Coverity 6.6. Perhaps most surprising is how the two solutions (both static analysis tools for C# that aim to improve quality and security) are so different and yet so complementary.
Continuous Testing Meets the Classroom at Code.orgSauce Labs
Code.org's Brian Jordan, a Software Engineer, takes the audience for a fun tour of Code.org’s continuous, automated testing suite. Brian discusses how Code.org approaches testing throughout the product development cycle, given their unique testing challenges—developing interactive, game-like curriculum for just the types of browsers you’d expect to find in school computer labs—from Internet Explorer 9 to iPads across 40+ languages.
This document summarizes a presentation about babysitting your ORM with a custom TFS build. The presentation discusses integrating ORM performance analysis into your ALM process using TFS and a profiling tool. It reviews ORMs and CI/TFS, demonstrates why measuring an ORM's behavior is important using examples, and shows a demo of writing tests, committing code through a gated check-in, and viewing profiling results on individual tests to detect issues like N+1 queries. The goal is to apply simple ideas and best practices to gain real, measurable ROI from monitoring ORM performance in your builds and tests.
1.microsoft visual studio 2010 test managerAshwin Jujgar
The document discusses Microsoft Visual Studio 2010 and Test Manager. It provides an overview of Visual Studio Team System 2010 and its tools for software development, testing, and management. It also describes the capabilities of Microsoft Test Manager for test planning, case management, execution and defect tracking. Finally, it demonstrates some of these capabilities through a test planning and execution demo.
This document discusses challenges with automated unit and integration testing involving databases. It presents RoundhousE and NDbUnit as tools that help address these challenges by managing database schema changes and ensuring data is in a known state before tests. Examples of how these tools work would be helpful to understand how they automate testing of database-related code.
testing is an important part of programming and software engineering. In this slide, I share insight on how to get started with writing tests in Django
These slides provide the high-level results of our comparison of FxCop and the Coverity platform. We used a third party codebase of approx. 100k lines of code and analyzed it using the "fxcop" from Visual Studio 2013 and Coverity 6.6. Perhaps most surprising is how the two solutions (both static analysis tools for C# that aim to improve quality and security) are so different and yet so complementary.
Continuous Testing Meets the Classroom at Code.orgSauce Labs
Code.org's Brian Jordan, a Software Engineer, takes the audience for a fun tour of Code.org’s continuous, automated testing suite. Brian discusses how Code.org approaches testing throughout the product development cycle, given their unique testing challenges—developing interactive, game-like curriculum for just the types of browsers you’d expect to find in school computer labs—from Internet Explorer 9 to iPads across 40+ languages.
Static analysis is a technique that analyzes source code without executing it to find useful information. It works by using tools to capture how code is compiled and then analyzes every path through the code using checkers to find defects like crashes, memory issues and security vulnerabilities. It is beneficial because it can find problems early in the development process when they are cheaper to fix, and the analysis can be done continuously even when developers are not working. Static analysis fits into the software development lifecycle by integrating with activities like code checking, nightly builds, testing and security audits to surface defects.
Approval Tests in Action: A LEGO Exercise and an Experience Reporthouseofyin
This document describes an exercise using LEGO pieces to demonstrate approval testing. It had participants build LEGO figures according to criteria in round 1. In round 2, they wrote tests to validate the criteria. In round 3, they validated a copy of their round 1 solution. The document then discusses approval testing and provides examples of how it can detect bugs and new features. It notes benefits like easier to understand tests and testing otherwise untestable code. It also discusses applicability and weaknesses like lack of isolation.
Automated Testing: Obstacles, Pitfalls, and DangersStephen Ritchie
The document discusses the motivation, principles, and obstacles of automated testing. It motivates automated testing by noting how it provides visibility into problems, detects issues early, and acts as an advance warning system. The principles discussed are having tests that are zero configuration, fast, provide clear results, and are easy to maintain. Obstacles covered include tests becoming too specific over time, reliance on system time/date, dependency on databases changing test data, and tests becoming too coupled through overuse of reuse. Examples are provided to illustrate the points.
This document provides an overview of common tools used for test automation, including frameworks, runners, drivers, reporting tools and build systems. It discusses factors to consider like the technology stack, skills of those writing and running tests, and how test results will be viewed. Popular automation stacks like HP QTP, FitNesse, Eclipse/JUnit/Selenium/Hudson and Cucumber are described. UI drivers like Selenium, Watir and desktop testing tools are also covered. Common challenges around test design, organization and synchronization are discussed along with approaches to address them.
Scala Bay Meetup - The state of Scala code style and qualityJaime Jorge
Questions:
• What are the current Scala code styles?
• Are we respecting them? An analysis of Scala Open Source projects using Codacy
• What might become best practices/standard?
DevOpsDaysRiga 2017 ignite: Mikhail Iljin - DevOps meets Data Science - how t...DevOpsDays Riga
Big data, data science, machine learning is coming to a lot of companies. Everyone is used to the creation of ordinary software, but BD/DS/ML requires special care. Managers and developers may get unfamiliar problems and I want to tell you about them and solutions - no money and nerves should be wasted.
Everyone has heard of data science, machine learning and big data. Many companies are starting to build up teams and run projects. Everyone knows how to develop, deliver and deploy ordinary software, but data-driven software is a different animal. Scientists, developers and managers may not be familiar with the issues that may come up.
Let’s face it: Best Practices are too many to really know them all and choose which ones should be applied first. Does your telephone ring all the time? Do your users ask for that “quick report” that instead takes ages and keeps changing every time you think it’s done? Have you ever thought that in dire times avoiding Worst Practices could be a good starting point and you can leave fine tuning for a better future? If the answer is “yes”, then this session is for you: we will discover together how not to torture a SQL Server instance and we will see how to avoid making choices that in the long run could turn out to be not as smart as they looked initially.
David Day is seeking a position as a Quality Assurance Developer/Tester. He has a Bachelor's degree in Physics and over 2 years of experience as a Team Lead and SQA Engineer. His skills include programming languages like Java, Python, PHP, and technologies like Dojo, Selenium, and various testing frameworks. At his previous job, he developed automated regression tests, wrote over 300 test applications, and participated in the development cycle of three major software products.
This document discusses SQL Server worst practices related to design, development, installation, and administration. Some key worst practices highlighted include not normalizing database schemas, using dynamic SQL with hardcoded literals, installing SQL Server with default settings, relying on autogrow for disk space management, and having no monitoring or alerting configured. The document encourages learning from other's mistakes to avoid common pitfalls, and provides resources for best practices analysis and SQL Server troubleshooting.
Dave Haeffner's Proven Method to Grading the Quality of Selenium TestsApplitools
** Watch Dave's full session recording here: https://youtu.be/IjGDxXCaDnE **
So you've written your fair share of Selenium tests.
Perhaps you've dabbled with Page Objects, Wait Strategies (aka Implicit and/or Explicit Waits), and you feel confident about your locators. Your test code might be in pretty good shape -- able to work reliably as time marches on and the application under test continues to evolve and your testing needs continue grow with it.
But how do you *know*? It's not like there is a quantitative way to measure this.
Or is there?
Watch Selenium expert Dave Haeffner as he steps through the core tenets of good test and page object design, locators, and a repeatable and quantitative approach for assessing your test code.
When you're done, you'll be able to see how your tests and page objects stack up, and what changes are needed to help them stand the test of time.
This document discusses unit testing and mock frameworks. It defines common terms like unit test, fake, stub, and mock. It describes the strengths and weaknesses of unit testing. It then introduces TypeMock as a mock framework that can fake static, sealed, or non-public elements without requiring design changes for testability. The document also briefly debates the pros and cons of dictating design for testability and mentions some research on the benefits of test-driven development.
.NET Unit Testing w/ Microsoft Fakes (TechCamp Memphis Spring 2012)lancehilliard
This document discusses .NET unit testing with Microsoft Fakes. It explains why unit testing is important to protect code from changes over time. A unit is the method being tested along with its isolated dependencies. Microsoft Fakes allows stubbing and shimming dependencies to isolate the unit and test different scenarios. Fakes generates stubs for well-designed dependencies and shims for poorly-designed ones, with some performance overhead. The document provides contact information and recommends additional reading on isolating tests and professional coding standards.
This document discusses PHP, QA tools like PHPUnit and Selenium, and the continuous integration tool Jenkins. It provides an overview of how to set up Jenkins and get started with continuous integration for a PHP project. Key steps include installing plugins, configuring the first job to run tests via Ant or PHPUnit scripts on a schedule or commit hooks, and tips for using PHPUnit including data providers and testing exceptions. Issues with testing CodeIgniter controllers and Selenium are also mentioned.
Property-based testing (PBT) focuses on testing specifications rather than implementations. It uses random testing against properties expressed as code to generate many test cases, reducing testing effort. PBT represents a system as states, commands to transition between states, and properties relating commands to expected states. This allows effective testing of stateful systems. PBT has been used successfully for concurrency, distributed systems, and finding bugs unit tests missed. Popular PBT libraries include Scalacheck, QuickCheck, and Hypothesis.
This is the presentation we gave in 2009 during Agile Testing Days in Berlin. Even though it is already more than 2 years old, many things we said during the talk are very valid today. Some things did not change at all.
The document discusses best practices for implementing programming languages including: defining the grammar, scoping rules, validation, execution, and editor integration. It provides tips on using syntactic predicates over backtracking, data types instead of terminals, concise modular grammars, leveraging indexes for scoping, loose grammars with strict validation, dependency injection, and emphasizing testing.
This document discusses how to achieve continuous delivery through injecting testing at various stages of the software development lifecycle. It outlines the goals of continuous delivery as better quality software, finding and fixing defects faster, and minimizing human error. It then describes the foundations for continuous delivery as design, development, acceptance, automation, monitoring, performance, multi-variant testing, and immunization. Throughout each stage, testing plays a key role in providing feedback, collaborating with teams, and facilitating excellence.
This document discusses best practices for team-based database development using version control. It emphasizes that all database code and configuration should be stored in version control for collaboration and risk reduction. The document recommends standards for naming conventions, coding styles, and development processes. It also demonstrates how to configure tools to support automation and efficient workflow within development teams. Effective communication, coordination, and adherence to source control principles are key to smooth team collaboration on database projects.
Static analysis is a technique that analyzes source code without executing it to find useful information. It works by using tools to capture how code is compiled and then analyzes every path through the code using checkers to find defects like crashes, memory issues and security vulnerabilities. It is beneficial because it can find problems early in the development process when they are cheaper to fix, and the analysis can be done continuously even when developers are not working. Static analysis fits into the software development lifecycle by integrating with activities like code checking, nightly builds, testing and security audits to surface defects.
Approval Tests in Action: A LEGO Exercise and an Experience Reporthouseofyin
This document describes an exercise using LEGO pieces to demonstrate approval testing. It had participants build LEGO figures according to criteria in round 1. In round 2, they wrote tests to validate the criteria. In round 3, they validated a copy of their round 1 solution. The document then discusses approval testing and provides examples of how it can detect bugs and new features. It notes benefits like easier to understand tests and testing otherwise untestable code. It also discusses applicability and weaknesses like lack of isolation.
Automated Testing: Obstacles, Pitfalls, and DangersStephen Ritchie
The document discusses the motivation, principles, and obstacles of automated testing. It motivates automated testing by noting how it provides visibility into problems, detects issues early, and acts as an advance warning system. The principles discussed are having tests that are zero configuration, fast, provide clear results, and are easy to maintain. Obstacles covered include tests becoming too specific over time, reliance on system time/date, dependency on databases changing test data, and tests becoming too coupled through overuse of reuse. Examples are provided to illustrate the points.
This document provides an overview of common tools used for test automation, including frameworks, runners, drivers, reporting tools and build systems. It discusses factors to consider like the technology stack, skills of those writing and running tests, and how test results will be viewed. Popular automation stacks like HP QTP, FitNesse, Eclipse/JUnit/Selenium/Hudson and Cucumber are described. UI drivers like Selenium, Watir and desktop testing tools are also covered. Common challenges around test design, organization and synchronization are discussed along with approaches to address them.
Scala Bay Meetup - The state of Scala code style and qualityJaime Jorge
Questions:
• What are the current Scala code styles?
• Are we respecting them? An analysis of Scala Open Source projects using Codacy
• What might become best practices/standard?
DevOpsDaysRiga 2017 ignite: Mikhail Iljin - DevOps meets Data Science - how t...DevOpsDays Riga
Big data, data science, machine learning is coming to a lot of companies. Everyone is used to the creation of ordinary software, but BD/DS/ML requires special care. Managers and developers may get unfamiliar problems and I want to tell you about them and solutions - no money and nerves should be wasted.
Everyone has heard of data science, machine learning and big data. Many companies are starting to build up teams and run projects. Everyone knows how to develop, deliver and deploy ordinary software, but data-driven software is a different animal. Scientists, developers and managers may not be familiar with the issues that may come up.
Let’s face it: Best Practices are too many to really know them all and choose which ones should be applied first. Does your telephone ring all the time? Do your users ask for that “quick report” that instead takes ages and keeps changing every time you think it’s done? Have you ever thought that in dire times avoiding Worst Practices could be a good starting point and you can leave fine tuning for a better future? If the answer is “yes”, then this session is for you: we will discover together how not to torture a SQL Server instance and we will see how to avoid making choices that in the long run could turn out to be not as smart as they looked initially.
David Day is seeking a position as a Quality Assurance Developer/Tester. He has a Bachelor's degree in Physics and over 2 years of experience as a Team Lead and SQA Engineer. His skills include programming languages like Java, Python, PHP, and technologies like Dojo, Selenium, and various testing frameworks. At his previous job, he developed automated regression tests, wrote over 300 test applications, and participated in the development cycle of three major software products.
This document discusses SQL Server worst practices related to design, development, installation, and administration. Some key worst practices highlighted include not normalizing database schemas, using dynamic SQL with hardcoded literals, installing SQL Server with default settings, relying on autogrow for disk space management, and having no monitoring or alerting configured. The document encourages learning from other's mistakes to avoid common pitfalls, and provides resources for best practices analysis and SQL Server troubleshooting.
Dave Haeffner's Proven Method to Grading the Quality of Selenium TestsApplitools
** Watch Dave's full session recording here: https://youtu.be/IjGDxXCaDnE **
So you've written your fair share of Selenium tests.
Perhaps you've dabbled with Page Objects, Wait Strategies (aka Implicit and/or Explicit Waits), and you feel confident about your locators. Your test code might be in pretty good shape -- able to work reliably as time marches on and the application under test continues to evolve and your testing needs continue grow with it.
But how do you *know*? It's not like there is a quantitative way to measure this.
Or is there?
Watch Selenium expert Dave Haeffner as he steps through the core tenets of good test and page object design, locators, and a repeatable and quantitative approach for assessing your test code.
When you're done, you'll be able to see how your tests and page objects stack up, and what changes are needed to help them stand the test of time.
This document discusses unit testing and mock frameworks. It defines common terms like unit test, fake, stub, and mock. It describes the strengths and weaknesses of unit testing. It then introduces TypeMock as a mock framework that can fake static, sealed, or non-public elements without requiring design changes for testability. The document also briefly debates the pros and cons of dictating design for testability and mentions some research on the benefits of test-driven development.
.NET Unit Testing w/ Microsoft Fakes (TechCamp Memphis Spring 2012)lancehilliard
This document discusses .NET unit testing with Microsoft Fakes. It explains why unit testing is important to protect code from changes over time. A unit is the method being tested along with its isolated dependencies. Microsoft Fakes allows stubbing and shimming dependencies to isolate the unit and test different scenarios. Fakes generates stubs for well-designed dependencies and shims for poorly-designed ones, with some performance overhead. The document provides contact information and recommends additional reading on isolating tests and professional coding standards.
This document discusses PHP, QA tools like PHPUnit and Selenium, and the continuous integration tool Jenkins. It provides an overview of how to set up Jenkins and get started with continuous integration for a PHP project. Key steps include installing plugins, configuring the first job to run tests via Ant or PHPUnit scripts on a schedule or commit hooks, and tips for using PHPUnit including data providers and testing exceptions. Issues with testing CodeIgniter controllers and Selenium are also mentioned.
Property-based testing (PBT) focuses on testing specifications rather than implementations. It uses random testing against properties expressed as code to generate many test cases, reducing testing effort. PBT represents a system as states, commands to transition between states, and properties relating commands to expected states. This allows effective testing of stateful systems. PBT has been used successfully for concurrency, distributed systems, and finding bugs unit tests missed. Popular PBT libraries include Scalacheck, QuickCheck, and Hypothesis.
This is the presentation we gave in 2009 during Agile Testing Days in Berlin. Even though it is already more than 2 years old, many things we said during the talk are very valid today. Some things did not change at all.
The document discusses best practices for implementing programming languages including: defining the grammar, scoping rules, validation, execution, and editor integration. It provides tips on using syntactic predicates over backtracking, data types instead of terminals, concise modular grammars, leveraging indexes for scoping, loose grammars with strict validation, dependency injection, and emphasizing testing.
This document discusses how to achieve continuous delivery through injecting testing at various stages of the software development lifecycle. It outlines the goals of continuous delivery as better quality software, finding and fixing defects faster, and minimizing human error. It then describes the foundations for continuous delivery as design, development, acceptance, automation, monitoring, performance, multi-variant testing, and immunization. Throughout each stage, testing plays a key role in providing feedback, collaborating with teams, and facilitating excellence.
This document discusses best practices for team-based database development using version control. It emphasizes that all database code and configuration should be stored in version control for collaboration and risk reduction. The document recommends standards for naming conventions, coding styles, and development processes. It also demonstrates how to configure tools to support automation and efficient workflow within development teams. Effective communication, coordination, and adherence to source control principles are key to smooth team collaboration on database projects.
Developers don’t even question the need for source control as part of their application life cycle management. But DBAs and database developers just don’t look at their databases in the same way as code. However, if you want to get good coordination between your application code and database, if you want to start to automate your database deployments, you need to treat your database like code. This session will demonstrate different mechanisms for getting a database into source control in order to begin to control your database in the same way you control your code.
Grant Fritchey Justin Caldicott - Best practices for database deploymentsRed Gate Software
This document discusses best practices for database deployments. It recommends treating the database like code by putting it under source control and integrating it with the development process. A well-defined, repeatable deployment process is key, working backwards from production and testing changes at each stage. Automation helps speed the process and remove human errors. The overall goal is a tightly coupled, automated workflow that moves database changes reliably through environments like development, testing and production.
The document discusses best practices for database deployments. It recommends treating the database like code by putting it under source control and defining a repeatable deployment process. The process should include deploying the database prior to the application, validating changes via testing, and automating deployments. Regularly moving changes through development, testing, and production environments ensures tight integration between the database and application.
The document summarizes the environments, processes, tools, and projects used at Discovery Life as a Java developer. Key points include:
- Development environments included local, DEV, QA, and production.
- A waterfall process was used with requirements, analysis, development, testing, and quarterly deployments.
- Source control used GIT. Build tools were custom but based on Ant. Unit testing was required.
- The developer was "hands off" from business analysis, database work, administration, infrastructure, and architecture.
- Technical specifications depicted requirements using UML diagrams. Design patterns like factory and singleton were used.
- The developer worked on claims and finance projects and as part of a collaborative team under a
This document provides a case study on a project created using open source technology. It discusses analyzing project goals and resources, evaluating open source options based on total cost of ownership, implementing a solution using LAMP stack, and lessons learned. The project was developed using Linux, Apache, MySQL, and PHP based on the needs of a low budget, ability to invest in internal skills, and reduce dependency on external trends. Key steps included preparing the Linux server, using version control and local testing, and engaging the open source community for support.
In this webinar, Dave Haeffner (Elemental Selenium, USA) discusses how to:
- Build an integrated feedback loop to automate test runs and find issues fast
- Setup your own infrastructure or connect to a cloud provider
-Dramatically improve test times with parallelization
https://huddle.eurostarsoftwaretesting.com/resource/webinar/use-selenium-successfully/
Want to learn how to use Selenium from the ground up? This presentation will show you how to start from nothing and build out a well factored, maintainable, resilient, and parallelized set of tests that will run locally, on a Continuous Integration server, and in the cloud. These tests will not only work well, but exercise relevant functionality that matters to the business.
Software design with Domain-driven design Allan Mangune
The document discusses domain-driven software design and related concepts. It begins with an overview of monolithic architecture and modular monoliths. It then covers IdentityServer4 for centralized authentication. Next, it defines domain-driven design and the utility of domain models. It discusses ingredients for effective modeling like prototyping and collaboration. It also covers bounded contexts, entities, value objects, and repositories. Finally, it provides tips for optimizing entities and database operations.
How To Use Selenium Successfully (Java Edition)Dave Haeffner
The document provides a 10 step guide to successfully using Selenium for automated testing. It begins by defining a test strategy and choosing a programming language. It then covers Selenium fundamentals like common actions and locator strategies. The next steps include writing the first test, making tests reusable and resilient, and packaging tests into a framework. It concludes by adding cross-browser execution and building an automated feedback loop through continuous integration. The goal is to write business-valuable tests that can run across browsers and be maintained by a team.
Driving application development through behavior driven developmentEinar Ingebrigtsen
This document discusses Behavior Driven Development (BDD) and how it can be used to drive application development. It introduces BDD, focusing on behaviors of the system rather than tests. It discusses key aspects of BDD like Gherkin, units, test doubles, writing testable code, frameworks like SpecFlow and recommended reading. The overall message is that BDD changes the way software is developed by shifting the focus to behaviors and improving collaboration.
Sauce Labs hosted a Selenium bootcamp webinar with guest speaker Dave Haeffner. This presentation will give you a basis for the detail given in Dave's like titled E-book and get you started with Selenium.
Beginners overview of automated testing with Rspecjeffrey1ross
The document provides an overview of automated testing for beginning developers, covering testing basics like unit tests and code coverage, popular Ruby testing tools and techniques like RSpec and Capybara, the benefits of automated testing like improved code quality and efficiency, and strategies for testing models, controllers, and views. It also discusses testing patterns and principles like the inverted testing pyramid, page object pattern, and single responsibility principle.
Jose Luis Soria - XP2014 - Designing a Release PipelineJose Luis Soria
This document discusses designing a release pipeline. It begins by defining key concepts like components, sub-pipelines, stages, environments, and steps. It then provides tips and considerations for identifying each of these elements to build out a release pipeline. The document emphasizes automating as much as possible, using virtualization, and evolving the pipeline over time based on feedback and lessons learned.
In this DNN-Connect 2019 session, I walk the audience through many of the most common things that we've run into over the years when helping clients with their DNN websites. You'll see some of the most common worst practices and how to resolve them.
Dev ops ci-ap-is-oh-my_security-gone-agile_ut-austinMatt Tesauro
An overview of how to change security from a reactive part of the org to a collaborative part of the agile development process. Using concepts from agile and DevOps, how can applicaton security get as nimble as product development has become.
Similar to Part of the DLM story: Get your Database under Source Control - SQL In The City (20)
The future of DevOps: fully left-shifted deployments with version control and...Red Gate Software
Join us to see Redgate's latest database DevOps innovations, which empower developers to code in the IDEs of their choice, version control database changes in plain SQL, and easily validate their changes against a masked copy of production as soon as they make the change.
By integrating cloning technology into proven developer workflows, Redgate:
• Provides a platform for easy and safe experimentation and innovation
• Reduces time to market for changes by removing manual work and enabling Continuous Delivery
• Supports continuous quality with static code analysis and automated testing functionality
Kendra Little will show you Redgate's recent innovations in action and give you a picture of where Database DevOps is going, and why.
Embracing DevOps through database migrations with FlywayRed Gate Software
"Evolutionary Database Design" is the best phrase to describe database migrations. But what do we know about database migrations using PostgreSQL containers?
This session will provide you with answers and guidelines to get you started with Database DevOps practices for your organization. You will learn the aspects, methods, and strategies to build and manage your database deployments through CI/CD pipelines with open source tools like Flyway, Jenkins, and Kubernetes.
You will be able to build your first database migration through a CI/CD pipeline at the end of this session.
Discover how Database DevOps and Octopus Deploy enable your organization to increase efficiency, reduce errors and get the most from your customer infrastructures.
Redgate Solution Architect, Chris Unwin will be joined by Octopus Deploy Continuous Delivery Architect, Ryan Rousseau as they demo:
• Multi tenancy deployments
• Tailoring release artifacts
• Effective Monitoring across your customer estates
A leading global bank, with a worldwide network of financial and business centers, Mizuho prides itself on their "customer first" principle.
James Phillips, VP of Corporate Technology at Mizuho, joins us to share how utilizing Database DevOps enables them to adapt quickly to market changes, with consistent and consolidated processes.
You will hear Mizuho’s Database DevOps transformation story first-hand, including:
• What prompted them to introduce Database DevOps?
• How did they get started?
• How does Database DevOps enhance their “customer first” principle?
• What were the biggest obstacles they had to overcome?
• What business benefits have they seen?
• What are the next steps in their DevOps journey?
Setting up monitoring for your SQL Server instances can be tough.
In this webinar, Microsoft MVP, Grant Fritchey and Senior Software Engineer for SQL Monitor, Jeremiah Peschka will walk you through the seven steps you need to perform in order to accomplish this challenge.
Knowing what’s happening on your servers is vital to ensuring business continuity, and the steps shared here will assist you through that process. We’ll show you the best way to set up monitoring on your environment, and how Redgate SQL Monitor provides a powerful and fast way of achieving this.
We’re excited to announce that Redgate has introduced a new workflow for both our SQL Server and Oracle DevOps solutions. This new workflow combines the state-based development experience implemented in SQL Source Control and Source Control for Oracle with the customizable power of migrations-based deployments.
The biggest benefit of the workflow is that customers may begin their DevOps journey with the simpler state-based development approach when that fits their needs, with the knowledge that they can transition seamlessly to more robust migrations-based deployments when they are ready.
In this webinar, Chris Unwin and Kendra Little show you the new workflow in action with SQL Source Control and Azure DevOps.
You’ll learn:
· What the new workflow is
· Which scenarios in state-based model make the new work flow desirable, and how to know if it’s right for your team
· What it’s like to work with the new workflow – we promise plenty of demos!
Key findings from the 2020 state of database dev ops reportRed Gate Software
The results are in! Join our expert panel, Kendra Little, Kellyn Pot’Vin Gorman & Grant Fritchey, to dig into key findings from Redgate’s fourth annual State of Database DevOps Report and learn how to use these insights to drive improvements in your own software development process.
Our webinar panel this year includes specialists with expertise in both Oracle and SQL Server, as well as experience implementing and managing Agile methodologies and compliant database DevOps in Enterprise environments.
We will share key findings and insights from this year’s report, which received input from more than two thousand developers, DBAs, and IT leaders worldwide, representing all industry verticals. Topics will include:
• Frequent database deployments are increasing: 49% of respondents now report they deploy database changes to production weekly or more frequently;
• The two top perceived obstacles to implementing DevOps are now concerns about upskilling and disruption to existing workflows. We will discuss how business cases to implement database DevOps should address these concerns;
• Developers are now involved in the majority of production database deployments, continuing an increasing trend we have seen across four years of this study. We will discuss what this means for both developers and DBAs;
• Most respondents deploy changes to their most business-critical databases while the system is online. Those who perform all or nearly all deployments with the system online reported lower lead time for changes and lower defect rates. We will discuss why this makes sense and how teams achieve this;
• Respondents who report that it is easy to get a code review for database changes also report lower production defect rates and lower lead time for changes to be deployed to production. We will discuss how to optimize database code review for different organization and team sizes.
Your business depends on rapidly deploying high-quality changes to databases while minimizing risk to data.
Learn how to protect business-critical data and improve software delivery with Redgate’s Compliant Database DevOps solution, which extends DevOps processes to Microsoft SQL Server and Azure SQL Database.
Microsoft Data Platform MVPs Kendra Little, Steve Jones, Kathi Kellenberger and Grant Fritchey come together for this festive webinar special.
Our band of experts discuss their highlights and favourite memories from throughout the year, sharing their own personal moments of glory, biggest learnings, and hilarious bloopers.
PASS President Grant Fritchey is joined by fellow Microsoft MVPs Kendra Little, Steve Jones and Kathi Kellenberger to discuss their highlights and learnings from PASS Summit 2019, the largest Microsoft Data Platform conference.
Quality in Software Development: Anglia Ruskin UniversityRed Gate Software
The document discusses what is involved in creating a quality product, focusing on software development. It lists the typical phases of requirements analysis, development, design, testing, and release. It emphasizes that quality involves short feedback loops, collaboration, and evolution. Quality is about providing value to customers. Maintainability, reusability, and testability are important factors if considering quality from the perspectives of other developers who will work with the code. References are provided for further reading on quality software management principles and approaches.
How SQL Change Automation helps you deliver value fasterRed Gate Software
Learn how Redgate tools enable you to speed up software delivery with reliable, repeatable processes that remove the database bottleneck. Learn how you can empower your developers to innovate without sacrificing compliance, and bring DBAs into the SDLC early at critical review points.
Microsoft's Principal Cloud Advocate & DevOps Lead Abel Wang and Redgate's Steve Jones cover:
- What is DevOps?
- How to explain the value of DevOps to both leadership and engineers
- Tips for advocating for DevOps as part of your 2020 planning
- How other organizations have had success implementing DevOps
- Lessons learned from Microsoft's DevOps transformation
In this session, you will learn the difference between Azure SQL Database, SQL Managed Instances, Elastic Pools, and SQL Virtual Machines. You will learn how to use tools to test migrations for issues before you start the migration process. You will learn how to successfully migrate your database schema and data to the cloud. Finally, you will learn how to determine which performance tier is a good starting point for your existing workload(s) and how to monitor your workload overtime to make sure your users have a great experience while you save as much money as possible.
The Ultimate Guide to Choosing and Implementing the Right Monitoring ToolRed Gate Software
Choosing the right monitoring tool for your organization goes beyond feature comparison and quite often even price. While you will likely have a budget to stick to and need to ensure the costs of the tool don’t exceed it, there are other factors you should consider when selecting the right tool for your organization.
Drawing on his 20 years’ experience in IT, Microsoft MVP Grant Fritchey explores in this presentation the following aspects of your monitoring selection process:
- Quantifying why change makes sense with monitoring
- Implementation hurdles and how to overcome them
- How to demonstrate success with your monitoring initiative after purchase
Everything You Need to Know About the 2019 DORA Accelerate State of DevOps Re...Red Gate Software
Each year, the DevOps Research and Assessment group (DORA) publishes critical research revealing the impact of DevOps on organizations of all sizes. The findings show what makes some teams successful at DevOps, while others fall behind.
Jez Humble, a founding member of DORA well known for his groundbreaking research on IT performance, and Redgate’s Microsoft MVP Steve Jones offer the latest insights from the 2019 Accelerate State of DevOps Report – and what they mean for your organization and career.
Using Redgate, AKS and Azure to bring DevOps to your databaseRed Gate Software
Practical solutions on how to bring DevOps to your database including:
- The importance of getting your database code into source control
- How to test your database changes
- Tools you can use to automate build and test processes
- How to build an automated deployment process for your database with Redgate tools
- How to embrace using Azure Kubernetes Services (AKS) in your deployment pipeline
- Deploying your entire pipeline as and when it is needed from Dev to Prod saving your organisation money
Using Redgate, AKS and Azure to bring DevOps to your DatabaseRed Gate Software
Join Hamish Watson and Rob Sewell to learn practical solutions on how to bring DevOps to your database, including:
• The importance of getting your database code into source control
• How to test your database changes
• Tools you can use to automate build and test processes
• How to build an automated deployment process for your database with Redgate tools
• How to embrace using Azure Kubernetes Services (AKS) in your deployment pipeline
• Deploying your entire pipeline as and when it is needed from Dev to Prod saving your organisation money
Database upgrades and data in general are often the most complicated part of your deployment process, so having a robust deployment path and checks before getting to production is very important.
The demos will showcase practical solutions that can help you and your team bring DevOps to your database using SQL Source Control, infrastructure as code, docker containers and SQL Change Automation – all leading up to a fully automated test and deployment process.
This will be a fun-filled fast paced hour and you will learn some new skills which will bring immediate benefit to your organization.
How to Pitch a Software Development Initiative and Ignite Culture ChangeRed Gate Software
You’ve got a great idea for transforming software development or IT processes in your organization, but you’re not sure how to get buy-in from key stakeholders, or how to change your company culture.
In this session, Microsoft MVP Ike Ellis will draw on his experience as a consultant and leader in software development to give you real-world tips to define, shape, and share your pitch successfully. Whether you are launching a revolutionary new initiative or expanding an existing effort to improve your software development, Ike’s tips will help you create a plan to effect change in your teams.
How Standard Bank overcame technical and cultural challenges to implement database CI/CD!
Redgate’s Grant Fritchey talks to James Grant from Standard Bank about implementing continuous integration and continuous deployment to their databases. Join us to hear about the challenges they faced along the way, how they overcame them, and the benefits they’re now seeing. In this session you’ll learn about:
• Addressing management concerns such as the high cost of failure, protecting business-critical data, and difficulty tracking changes
• Overcoming resistance to change in the teams and getting change past the “old guard”
• Brown-field vs green-field CI/CD pipelines and the technical challenges of bringing existing database solutions onto a pipeline
• Using database unit testing as more than just a way to limit bugs and errors
Microservice Teams - How the cloud changes the way we workSven Peters
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
Odoo releases a new update every year. The latest version, Odoo 17, came out in October 2023. It brought many improvements to the user interface and user experience, along with new features in modules like accounting, marketing, manufacturing, websites, and more.
The Odoo 17 update has been a hot topic among startups, mid-sized businesses, large enterprises, and Odoo developers aiming to grow their businesses. Since it is now already the first quarter of 2024, you must have a clear idea of what Odoo 17 entails and what it can offer your business if you are still not aware of it.
This blog covers the features and functionalities. Explore the entire blog and get in touch with expert Odoo ERP consultants to leverage Odoo 17 and its features for your business too.
An Overview of Odoo ERP
Odoo ERP was first released as OpenERP software in February 2005. It is a suite of business applications used for ERP, CRM, eCommerce, websites, and project management. Ten years ago, the Odoo Enterprise edition was launched to help fund the Odoo Community version.
When you compare Odoo Community and Enterprise, the Enterprise edition offers exclusive features like mobile app access, Odoo Studio customisation, Odoo hosting, and unlimited functional support.
Today, Odoo is a well-known name used by companies of all sizes across various industries, including manufacturing, retail, accounting, marketing, healthcare, IT consulting, and R&D.
The latest version, Odoo 17, has been available since October 2023. Key highlights of this update include:
Enhanced user experience with improvements to the command bar, faster backend page loading, and multiple dashboard views.
Instant report generation, credit limit alerts for sales and invoices, separate OCR settings for invoice creation, and an auto-complete feature for forms in the accounting module.
Improved image handling and global attribute changes for mailing lists in email marketing.
A default auto-signature option and a refuse-to-sign option in HR modules.
Options to divide and merge manufacturing orders, track the status of manufacturing orders, and more in the MRP module.
Dark mode in Odoo 17.
Now that the Odoo 17 announcement is official, let’s look at what’s new in Odoo 17!
What is Odoo ERP 17?
Odoo 17 is the latest version of one of the world’s leading open-source enterprise ERPs. This version has come up with significant improvements explained here in this blog. Also, this new version aims to introduce features that enhance time-saving, efficiency, and productivity for users across various organisations.
Odoo 17, released at the Odoo Experience 2023, brought notable improvements to the user interface and added new functionalities with enhancements in performance, accessibility, data analysis, and management, further expanding its reach in the market.
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
14 th Edition of International conference on computer visionShulagnaSarkar2
About the event
14th Edition of International conference on computer vision
Computer conferences organized by ScienceFather group. ScienceFather takes the privilege to invite speakers participants students delegates and exhibitors from across the globe to its International Conference on computer conferences to be held in the Various Beautiful cites of the world. computer conferences are a discussion of common Inventions-related issues and additionally trade information share proof thoughts and insight into advanced developments in the science inventions service system. New technology may create many materials and devices with a vast range of applications such as in Science medicine electronics biomaterials energy production and consumer products.
Nomination are Open!! Don't Miss it
Visit: computer.scifat.com
Award Nomination: https://x-i.me/ishnom
Conference Submission: https://x-i.me/anicon
For Enquiry: Computer@scifat.com
Project Management: The Role of Project Dashboards.pdfKarya Keeper
Project management is a crucial aspect of any organization, ensuring that projects are completed efficiently and effectively. One of the key tools used in project management is the project dashboard, which provides a comprehensive view of project progress and performance. In this article, we will explore the role of project dashboards in project management, highlighting their key features and benefits.
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Unlock the Secrets to Effortless Video Creation with Invideo: Your Ultimate G...The Third Creative Media
"Navigating Invideo: A Comprehensive Guide" is an essential resource for anyone looking to master Invideo, an AI-powered video creation tool. This guide provides step-by-step instructions, helpful tips, and comparisons with other AI video creators. Whether you're a beginner or an experienced video editor, you'll find valuable insights to enhance your video projects and bring your creative ideas to life.
The Key to Digital Success_ A Comprehensive Guide to Continuous Testing Integ...kalichargn70th171
In today's business landscape, digital integration is ubiquitous, demanding swift innovation as a necessity rather than a luxury. In a fiercely competitive market with heightened customer expectations, the timely launch of flawless digital products is crucial for both acquisition and retention—any delay risks ceding market share to competitors.
Preparing Non - Technical Founders for Engaging a Tech AgencyISH Technologies
Preparing non-technical founders before engaging a tech agency is crucial for the success of their projects. It starts with clearly defining their vision and goals, conducting thorough market research, and gaining a basic understanding of relevant technologies. Setting realistic expectations and preparing a detailed project brief are essential steps. Founders should select a tech agency with a proven track record and establish clear communication channels. Additionally, addressing legal and contractual considerations and planning for post-launch support are vital to ensure a smooth and successful collaboration. This preparation empowers non-technical founders to effectively communicate their needs and work seamlessly with their chosen tech agency.Visit our site to get more details about this. Contact us today www.ishtechnologies.com.au
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
The Rising Future of CPaaS in the Middle East 2024Yara Milbes
Explore "The Rising Future of CPaaS in the Middle East in 2024" with this comprehensive PPT presentation. Discover how Communication Platforms as a Service (CPaaS) is transforming communication across various sectors in the Middle East.
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
2. Goals
• Understand the value of version/source control
for databases
• Learn the tools, standards, patterns and best
practices needed to manage a database from
source control
• Identify the necessary flow within a team needed
to develop a database with source control
3. Get in touch
Steve Jones
www.voiceofthedba.com
sjones@sqlservercentral.com
@way0utwest
4. How many of you use version control for
your application code?
C#, ASP.NET, Javascript, VB.NET, etc.
5. How many of you use version control for
your application code?
database
18. Additional Reasons for Source Control
• Backup & Restore
• Undo
• Audit changes
• Sandbox
• Branching/Merging
19. Rules for Database Development
Never use a shared database for development.
Always Have a Single, Authoritative Source
For Your Schema.
Always Version Your Database.
20. The Ideal
• Each developer has a
dedicated environment with
a copy of the schema and
minimal data.
• A shared integration environment where all
developers’ changes are merged, available
for developer testing.
21. Patterns and Practices
• Get all your code
– Object DDL
– Assembly code
– Security grants and revokes
– Database configuration settings
– Jobs for your application
– Lookup data
22. Patterns and Practices
• Commit Early, Commit Often
• Use meaningful comments. Why, not what.
• Check for changes often
• Use common names and code patterns
• Use tools
• Branch Rarely
24. Teamwork
• Communication
o Team members need to be aware of (easily)
what others are doing.
• Coordination
o Teams need to work in a way that
complements each other.
25. Teamwork
• Communication
o Review each other’s code as you refactor
o Share knowledge
o Coordination
o Decide on common code styles and names
o And …
31. Best Practices
• Use version control for all code (including tests)
• Commit early, commit often
• Use tools
o If it’s hard, people don’t do it
• Train people
• Build often
35. Goals
• Understand the value of version/source control
for databases
• Learn the tools, standards, patterns and best
practices needed to manage a database from
source control
• Identify the necessary flow within a team needed
to develop a database with source control
36. Thanks for coming
www.voiceofthedba.com
sjones@sqlservercentral.com
@way0utwest
Want to try the tools you’ve just
seen? Come to our Hands-on Labs
37. References
• http://stackoverflow.com/questions/115369/do-you-use-source-control-for-your-
database-items
• http://www.codinghorror.com/blog/archives/001050.html
• http://www.codinghorror.com/blog/2008/02/get-your-database-under-version-
control.html
• http://www.ssw.com.au/ssw/Standards/Rules/RulesToBetterSQLServerData
bases.aspx
• http://odetocode.com/blogs/scott/archive/2008/01/30/three-rules-for-database-
work.aspx
• Check in early, check in often -
http://www.codinghorror.com/blog/2008/08/check-in-early-check-in-often.
html
• http://betterexplained.com/articles/a-visual-guide-to-version-control/
How many people in the audience use version control for their application code? Any of your front end code.
* Note number
Let’s ask the same question. How many of you use version control for your database code? For your tables, views, procedures? What about schemas? What about permissions and roles? What about cryptographic keys?
* Note number and difference.
Developers who refuse to use source/version control should be fired, simple as that. – top stack exchange
Isn’t this too much trouble for my crappy experimental program. - Drupal
Use source control because neither you nor your developers are perfect. – bottom stack exchange
There are no excuses where you should not use it. - makeuseof
If it’s not in source control, it doesn’t exist. - TroyHunt
http://programmers.stackexchange.com/questions/122150/how-can-i-convince-cowboy-programmers-to-use-source-control
http://www.makeuseof.com/tag/git-version-control-youre-developer/
http://www.mactech.com/articles/mactech/Vol.14/14.06/VersionControlAndTheDeveloper/index.html
http://drupal.org/node/299067
Developers who refuse to use source/version control should be fired, simple as that. – top stack exchange
Isn’t this too much trouble for my crappy experimental program. - Drupal
Use source control because neither you nor your developers are perfect. – bottom stack exchange
There are no excuses where you should not use it. - makeuseof
If it’s not in source control, it doesn’t exist. - TroyHunt
http://programmers.stackexchange.com/questions/122150/how-can-i-convince-cowboy-programmers-to-use-source-control
http://www.makeuseof.com/tag/git-version-control-youre-developer/
http://www.mactech.com/articles/mactech/Vol.14/14.06/VersionControlAndTheDeveloper/index.html
http://drupal.org/node/299067
Developers who refuse to use source/version control should be fired, simple as that. – top stack exchange
Isn’t this too much trouble for my crappy experimental program. - Drupal
Use source control because neither you nor your developers are perfect. – bottom stack exchange
There are no excuses where you should not use it. - makeuseof
If it’s not in source control, it doesn’t exist. - TroyHunt
http://programmers.stackexchange.com/questions/122150/how-can-i-convince-cowboy-programmers-to-use-source-control
http://www.makeuseof.com/tag/git-version-control-youre-developer/
http://www.mactech.com/articles/mactech/Vol.14/14.06/VersionControlAndTheDeveloper/index.html
http://drupal.org/node/299067
Developers who refuse to use source/version control should be fired, simple as that. – top stack exchange
Isn’t this too much trouble for my crappy experimental program. - Drupal
Use source control because neither you nor your developers are perfect. – bottom stack exchange
There are no excuses where you should not use it. - makeuseof
If it’s not in source control, it doesn’t exist. - TroyHunt
http://programmers.stackexchange.com/questions/122150/how-can-i-convince-cowboy-programmers-to-use-source-control
http://www.makeuseof.com/tag/git-version-control-youre-developer/
http://www.mactech.com/articles/mactech/Vol.14/14.06/VersionControlAndTheDeveloper/index.html
http://drupal.org/node/299067