Final frontier testinginproduction
•
0 likes•427 views
No tester wants to hear a developer say “It works on my machine!” because what it actually says is: “Since it worked on my development environment I assume it also works on your test environment hence you cannot possibly have found a bug." We know this not to be true, yet make the same assumption between environments in a later stage: We test our software on test environments and assume that our test results carry over to production. We are actually not testing the software in the setting where our users are facing it. To top it off, we spend a considerable amount of money trying to copy production. Managing test environments is often hard, complex and needs a lot of maintenance effort. A lot of people are already using techniques, which take testing into production like Beta Testing, A/B Testing or Monitoring as Testing. We intend to push the envelope a little further and additionally move acceptance testing, automated checks or exploration to the production stage. To do so we need to take several things into consideration, such as making sure test data does not mess up productive data and analytics, as well as hiding untested features from customers. In this talk you will learn about popular testing in production techniques. We also want to show you some strategies, which help tackling common constraints you will face and provide you with an approach to gradually shift your testing to production.
Report
Share
Report
Share
Download to read offline
Recommended
Stop! you're testing too much
Test automation has many advantages. It is a useful but imperfect practice with limitations that are hard to anticipate in a new project. There are many questions that teams find themselves asking throughout a project’s lifecycle:
- How do I get started?
- What should I automate?
- How do I collect the data?
- How do I run my tests when no one is around?
- Do I always need to run all of my tests?
- Do I need to keep my tests forever?
- Where does automation fit in the cadence of the team?
In this session we’ll discuss these question and some additional practical lessons learned from several years of building solutions that leverage test automation in both large and small environments.
Testing without assertions - #HUSTEF2019
Recheck-web ( https://github.com/retest/recheck-web) is a free Open Source test automation tool on basis of Selenium. It implements Golden Master testing, which makes for
– easy to create and maintain tests
– that are more complete
– and less fragile.
And on top of that it can make your test almost unbreakable and elements easy to address with a constant virtual id.
Learn how recheck-web works and train hands-on with some examples.
https://www.hustef.hu/speakerslist2019/speaker_dr-jeremias-rosler/
Unit testing for WordPress
- Unit testing involves writing code to test individual units or components of an application to ensure they perform as expected.
- The document discusses setting up a unit testing framework for WordPress plugins and themes using PHPUnit and WP-CLI. It provides steps to generate initial test files and install dependencies to support unit testing.
- Examples of writing unit tests are given, including how to structure tests with assertions to validate the behavior of functions and methods. Maintaining well-organized test files and cases is important for an effective testing suite.
Stress Test & Chaos Engineering
The document discusses stress testing and chaos engineering techniques to test the reliability, availability, and scalability of systems and services. It recommends starting with functional requirements and productivity, then stress testing services with increasing loads to identify breaking points and understand metrics. Fallback mechanisms need continuous testing to avoid outages. Chaos engineering techniques intentionally introduce failures to test infrastructure resilience to different failures like instance, availability zone, or region outages. Stress testing and chaos engineering are important to ensure systems can withstand failures and growing usage.
SophiaConf 2018 - P. Urso (Activeeon)
STAMP (Software Testing Amplification) is a suite of tools to increase testing capacity and detect bugs. It includes Descartes, which tests test cases against mutants to evaluate effectiveness, and DSpot, which aims to improve code coverage and mutation score by generating new test cases. CAMP (Configuration Amplification) executes test cases against multiple configurations, and Evocrash generates test cases to reproduce bugs found in production logs. The tools can be used standalone, with IDEs like Eclipse, or integrated into build tools like Maven and Jenkins to amplify testing practices and help improve quality.
Building tools to free up exploratory testers - appium conference talk
I have been a functional exploratory tester. I was motivated to move out of exploratory testing and go into automation. Thankfully, someone pulled me aside and told me - I am more suited to be a functional exploratory tester and I am business savvy. I didn't shy away from code. I worked closely with developers, my testing approach involved reading code (didn't write any) and brought in value to developers and to the business. I grew up as a tester being coached by experts, reading blogs from experts and learning that automation will help exploratory testers do more.
In my wait - I found very little effort that has gone in direction. I partnered with developers to be building some products.
I failed multiple times but here are my failed attempts
1. Tool for Social Media Driven Testing for Testers
2. Tool for mapping the heuristics and oracles to test ideas
3. A checklist tool for testing mobile apps and scoring on quality for start-ups
I would like to share
- The thinking behind building these tools and their value
- How purely focusing only on automation is taking away the possibility of building tools
- How I would love the community to start building tools
- How I can help and how they can help me
PgTAP Best Practices
So you've got testing religion, but the question now is, how do you test your database?
This tutorial introduces pgTAP, a comprehensive, easy-to-use test suite for PostgreSQL. We'll work from getting and installing pgTAP, to writing a simple test, to running the test and integrating it into your test environment. And then we really get into the fun stuff:
Testing scalar values
Testing error conditions and performance regressions
Testing database schemas, including tables, columns, constraints, indexes, triggers, etc.
Testing result sets
Testing procedures
Testing may sound like a dry topic, but my examples aren't! Come join the fun!
Test Driven Development: Why I hate it; but secretly love it.
Test Driven Development (TDD) involves writing failing tests first, then code to pass those tests, and refactoring code. The document discusses:
- Starting with a failing test and then making it pass by adding the minimum code needed. More tests are added that fail initially.
- Dependency injection improves flexibility by allowing dependencies to be passed into classes rather than created internally.
- TDD uses small, incremental "baby steps" by writing one test, making it pass, then adding another to drive the design and ensure changes don't break existing functionality. This results in stable, flexible code.
Recommended
Stop! you're testing too much
Test automation has many advantages. It is a useful but imperfect practice with limitations that are hard to anticipate in a new project. There are many questions that teams find themselves asking throughout a project’s lifecycle:
- How do I get started?
- What should I automate?
- How do I collect the data?
- How do I run my tests when no one is around?
- Do I always need to run all of my tests?
- Do I need to keep my tests forever?
- Where does automation fit in the cadence of the team?
In this session we’ll discuss these question and some additional practical lessons learned from several years of building solutions that leverage test automation in both large and small environments.
Testing without assertions - #HUSTEF2019
Recheck-web ( https://github.com/retest/recheck-web) is a free Open Source test automation tool on basis of Selenium. It implements Golden Master testing, which makes for
– easy to create and maintain tests
– that are more complete
– and less fragile.
And on top of that it can make your test almost unbreakable and elements easy to address with a constant virtual id.
Learn how recheck-web works and train hands-on with some examples.
https://www.hustef.hu/speakerslist2019/speaker_dr-jeremias-rosler/
Unit testing for WordPress
- Unit testing involves writing code to test individual units or components of an application to ensure they perform as expected.
- The document discusses setting up a unit testing framework for WordPress plugins and themes using PHPUnit and WP-CLI. It provides steps to generate initial test files and install dependencies to support unit testing.
- Examples of writing unit tests are given, including how to structure tests with assertions to validate the behavior of functions and methods. Maintaining well-organized test files and cases is important for an effective testing suite.
Stress Test & Chaos Engineering
The document discusses stress testing and chaos engineering techniques to test the reliability, availability, and scalability of systems and services. It recommends starting with functional requirements and productivity, then stress testing services with increasing loads to identify breaking points and understand metrics. Fallback mechanisms need continuous testing to avoid outages. Chaos engineering techniques intentionally introduce failures to test infrastructure resilience to different failures like instance, availability zone, or region outages. Stress testing and chaos engineering are important to ensure systems can withstand failures and growing usage.
SophiaConf 2018 - P. Urso (Activeeon)
STAMP (Software Testing Amplification) is a suite of tools to increase testing capacity and detect bugs. It includes Descartes, which tests test cases against mutants to evaluate effectiveness, and DSpot, which aims to improve code coverage and mutation score by generating new test cases. CAMP (Configuration Amplification) executes test cases against multiple configurations, and Evocrash generates test cases to reproduce bugs found in production logs. The tools can be used standalone, with IDEs like Eclipse, or integrated into build tools like Maven and Jenkins to amplify testing practices and help improve quality.
Building tools to free up exploratory testers - appium conference talk
I have been a functional exploratory tester. I was motivated to move out of exploratory testing and go into automation. Thankfully, someone pulled me aside and told me - I am more suited to be a functional exploratory tester and I am business savvy. I didn't shy away from code. I worked closely with developers, my testing approach involved reading code (didn't write any) and brought in value to developers and to the business. I grew up as a tester being coached by experts, reading blogs from experts and learning that automation will help exploratory testers do more.
In my wait - I found very little effort that has gone in direction. I partnered with developers to be building some products.
I failed multiple times but here are my failed attempts
1. Tool for Social Media Driven Testing for Testers
2. Tool for mapping the heuristics and oracles to test ideas
3. A checklist tool for testing mobile apps and scoring on quality for start-ups
I would like to share
- The thinking behind building these tools and their value
- How purely focusing only on automation is taking away the possibility of building tools
- How I would love the community to start building tools
- How I can help and how they can help me
PgTAP Best Practices
So you've got testing religion, but the question now is, how do you test your database?
This tutorial introduces pgTAP, a comprehensive, easy-to-use test suite for PostgreSQL. We'll work from getting and installing pgTAP, to writing a simple test, to running the test and integrating it into your test environment. And then we really get into the fun stuff:
Testing scalar values
Testing error conditions and performance regressions
Testing database schemas, including tables, columns, constraints, indexes, triggers, etc.
Testing result sets
Testing procedures
Testing may sound like a dry topic, but my examples aren't! Come join the fun!
Test Driven Development: Why I hate it; but secretly love it.
Test Driven Development (TDD) involves writing failing tests first, then code to pass those tests, and refactoring code. The document discusses:
- Starting with a failing test and then making it pass by adding the minimum code needed. More tests are added that fail initially.
- Dependency injection improves flexibility by allowing dependencies to be passed into classes rather than created internally.
- TDD uses small, incremental "baby steps" by writing one test, making it pass, then adding another to drive the design and ensure changes don't break existing functionality. This results in stable, flexible code.
Manual testing
Development)
- Define test strategy and approach
- Estimate test effort and schedule
- Identify risks and contingencies
- Define test environment
- Select tools and techniques
- Estimate test completion criteria
- Produce test plan document
Test planning involves:
- Defining the overall test strategy and approach
- Estimating the test effort and schedule
- Identifying risks and contingencies
- Defining the test environment requirements
- Selecting tools and techniques
- Estimating test completion criteria
- Producing the test plan document
The key outputs of test planning are:
- Test strategy and approach
- Test effort and schedule estimates
- Risks and contingencies plan
- Test environment
ic test engineering cost down in China
This document describes ATE test services offered in China at significantly lower costs than in the US. Engineering hourly and weekly rates are 50% lower, and turn-key test solutions including test planning, debugging, programming, and production support are available. Customized solutions can further reduce costs for production testing through techniques like dedicated test modules that minimize loadboard layers and ATE instruments needed.
Efficient And Effective Test Design
Pairwise and Combinatorial testing can dramatically improve the efficiency and effectiveness of both test design (identifying and document what to test) as well as test execution (the process of executing the test cases).
This presentation, by Justin Hunter, the founder of Hexawise, to members of TISQA, explains how these methods work, highlights empirical evidence that shows this method has been proven to more than double the number of defects found per tester hour in ten separate projects, and highlights a case study of a recent user of the Hexawise test design tool.
Test
This document outlines an agenda for presenting on software testing. It discusses the importance of testing code, different types of tests like unit tests, integration tests and acceptance tests. It also introduces the PHPUnit testing framework and how to write tests in PHPUnit. Specific techniques like test doubles and test-driven development are explained. Frameworks for testing code in Zend and CakePHP are also briefly mentioned.
Overcoming The Challenges Faced in Exploratory Testing
It is pretty evident from the name ‘Exploratory Testing’, that, it is the continuous process of learning through a cycle of trial and error. Unlike scripted testing, exploratory testing does not have test cases which can be executed and compared with the results. Rather, it is an intelligent way of testing which calls for innovation and individual thought process of the tester. This is also a reason why despite automation being the big word in the modern day, exploratory testing is a hot topic.
Howto Test A Patch And Make A Difference!
1. The document provides instructions on how to test patches for Drupal modules. It outlines the patch testing process which involves a developer submitting code changes as a patch file, the patch then being reviewed and tested by others, and feedback being provided.
2. The process aims to ensure code quality through multiple reviews of changes. Anyone can help with testing regardless of skill level.
3. Testing a patch involves downloading the patch file, applying it locally, testing the functionality, then providing feedback on the issue queue page. Proper documentation of results is important.
FAQ - why does my code throw a null pointer exception - common reason #1 Rede...
A common reason for Null Pointer Exceptions in Java is a variable redeclaration instead of instantiation. Learn what that means, how to avoid it, and how to spot it, in this presentation.
Read the full blog post: http://testerhq.com/post/blogs/javafortesters/2017-08-29-faq-null-pointer-exception/
Visit my Java Web Site: http://javafortesters.com
---
# FAQ - why does my code throw a null pointer exception - common reason #1 Redeclaration
- Using `@BeforeClass` or `@Before` can setup data for use in tests
- Any 'variables' we instantiate need to be 'fields' rather than variables
- We want to instantiate them in the setup method rather than redeclare them
---
# Example of the Problem
I know I will use an `Adder` in my test so I create it as a field:
~~~~~~~~
public class WhyCodeThrowsNullPointerExceptionTest {
Adder adder;
~~~~~~~~
I don't want to re-instantiate it each time so I make an `@BeforeClass` method to instantiate it:
~~~~~~~~
@BeforeClass
public static void setupAdder(){
Adder adder = new Adder();
}
~~~~~~~~
**Warning: Error in the above code**
---
# Semantic Error
I just made a Semantic coding error. This won't be caught by a compiler, but it will cause my `@Test` to fail with a Null Pointer Exception.
In the setup method I really wanted to assign a value to the field, instead I created an new variable with the same name.
# In General
- Try to write one test at a time so that if you have a problem it is easier to identify where the problem is
- Try to write working isolated tests and then refactor to a more general solution when you need it - that way, you know it was working, so you just have to work backwards to find out what went wrong
- Try to use automated IDE refactoring rather than move code around manually
- Use the IDE syntax highlighting to help spot any issues
iOS Unit Testing
A talk about unit testing for iOS apps. Part rambling introduction to test driven development, part examples of certain types of tests for iOS, and a brief mention of writing your tests using Kiwi.
Presentation13
The document outlines seven fundamental principles of software testing:
1. Exhaustive testing is unrealistic and risk-based testing is required.
2. Defects tend to cluster in specific high-risk modules.
3. Repeated identical tests become less effective at finding bugs over time ("pesticide paradox").
4. Early testing in development cycles better identifies requirements and design issues.
5. The absence of errors in testing does not prove correctness or ensure the software meets user needs.
6. Testing approaches depend on the context and type of software.
7. These principles form the foundation of effective software testing.
Understand regression testing
Regression testing is important to ensure new software changes do not break existing functionality. Automating regression testing helps manage the large number of test cases needed and speeds up release cycles. Key aspects of managing regression include establishing a baseline, comparing new results to the baseline, debugging failures efficiently, and automating testing processes to reduce human effort and testing time.
All you need to know about regression testing | David Tzemach
All you need to know about Regression testing| David Tzemach
1. Overview
2. What is “Regression” testing…?
3. When should you use it..?
4. How to implement..?
5. Test Recommendations
6. Considerations when building Regression tests
Test Reports
The document discusses various test reporting tools that testers use such as Pareto charts, cause-effect diagrams, and check sheets. It then provides examples of eight interim test reports that provide status updates on functional testing, defects uncovered versus corrected, and average age of uncorrected defects. The summaries provide testing metrics to analyze progress and identify issues.
Testing in Django
The document discusses testing in Django and provides an overview of writing tests from an evolutionary perspective. It begins by introducing the speaker and asking attendees to raise their hands based on their testing experience. It then defines what a test is, using an example of manually testing a function in the Python interpreter. It describes how tests can evolve to be automated and integrated into Django's testing framework. Finally, it outlines four key reasons for writing tests: to fix bugs only once, enable refactoring, serve as documentation, and clarify thinking.
Unit Testing
The document introduces the JUnit testing framework and discusses how automatic unit testing can help save time by dividing testing into smaller units and providing a uniform testing tool. It explains that unit testing involves dividing code into classes or related classes, then writing test cases that specify conditions, states, and behaviors to test before and after each change is made to verify expected results. The document also outlines the three steps - arrange, act, and assert - for writing test cases to set up object snapshots, invoke methods to create changes, and check final states match expectations.
Principles and Practices in Continuous Deployment at Etsy
This document discusses principles and practices of continuous deployment at Etsy. It describes how Etsy moved from deploying code changes every 2-3 weeks with stressful release processes, to deploying over 30 times per day. The key principles that enabled this are innovating continuously, resolving scaling issues quickly, minimizing recovery time from failures, and prioritizing employee well-being over stressful releases. Automated testing, deployment to staging environments, dark launches, and extensive monitoring allow for frequent, low-risk deployments to production.
Software testing overview by subbu
Testing is necessary to identify correctness, completeness, and quality of software. There are various testing techniques including white box testing which tests internal logic and structure based on code coverage, and black box testing which tests functionality based on requirements without knowledge of internal design. Equivalence partitioning is a black box technique that divides inputs into equivalence classes of data expected to produce the same outputs, helping minimize the number of test cases needed. How much testing is enough depends on risk factors like potential costs of failures. Exhaustive testing testing all combinations is not feasible due to the vast number of possibilities.
Software Testing_Overview
Testing is necessary to identify correctness, completeness, and quality of software. There are various techniques for testing software such as white box testing which tests internal logic and structure, and black box testing which tests without knowledge of internal design. Equivalence partitioning divides inputs into classes to minimize the number of test cases needed. Exhaustive testing all possible combinations is not feasible due to the large number of tests required. Risk-based testing prioritizes testing based on risk to the system to determine what to test first and most thoroughly.
Review of an open source unit test tool- Cucumber_Presentation
Unit testing validates individual units or components of software to ensure they perform as designed. Cucumber is a testing framework that uses plain English scenarios in a Given-When-Then format to test software. It supports various programming languages and serves as both documentation and automated tests. Cucumber scenarios are written in feature files, while step definitions contain the actual code to implement the scenarios in code. This allows ensuring scenarios pass by writing code to implement the steps.
Configuration testing
This document discusses configuration testing and management. Configuration testing involves testing software and systems on different hardware and software combinations to check for compatibility issues. It is important because the number of possible configurations is usually too large to fully test. Configuration management is also important for tracking what is being tested and different versions. Hardware and software configuration testing both help ensure compatibility and identify issues across environments.
Testing Hourglass at Jira Frontend - by Alexey Shpakov, Sr. Developer @ Atlas...
Alexey Shpakov presents on testing in Jira Frontend. He discusses the testing pyramid with unit, integration, and end-to-end tests. He then introduces the concept of a "testing hourglass" which adds deployment and post-deployment verification to the pyramid. Key aspects of each type of test are discussed such as using feature flags, monitoring for flaky tests, and gradual rollouts to reduce risk.
Manual testing visonia
Testing software is essential to ensure it works properly and performs as intended. Various testing levels are described from unit testing of individual components to system testing of integrated modules. An overview of the software development lifecycle is provided from requirements gathering to maintenance, and key testing activities are outlined at each stage like test planning, case design, execution, and reporting. Standard documents involved in testing are also summarized such as test plans, cases, and bug reports to track issues.
Tdd dev session
This document provides an overview of test-driven development (TDD) and the use of mock objects. It defines key TDD concepts like unit tests, test fixtures, test methods, and test suites. It explains that the goal of unit tests is to test individual classes and methods in isolation. The document discusses different types of testing like functionality testing, integration testing, and system testing. It emphasizes that unit tests using mock objects are the smallest and most focused type of testing. The document outlines the TDD process of writing a test, making it fail, writing code to pass the test, refactoring code, and repeating. It explains benefits of TDD like reducing bugs and enabling safe refactoring. It also discusses principles
More Related Content
What's hot
Manual testing
Development)
- Define test strategy and approach
- Estimate test effort and schedule
- Identify risks and contingencies
- Define test environment
- Select tools and techniques
- Estimate test completion criteria
- Produce test plan document
Test planning involves:
- Defining the overall test strategy and approach
- Estimating the test effort and schedule
- Identifying risks and contingencies
- Defining the test environment requirements
- Selecting tools and techniques
- Estimating test completion criteria
- Producing the test plan document
The key outputs of test planning are:
- Test strategy and approach
- Test effort and schedule estimates
- Risks and contingencies plan
- Test environment
ic test engineering cost down in China
This document describes ATE test services offered in China at significantly lower costs than in the US. Engineering hourly and weekly rates are 50% lower, and turn-key test solutions including test planning, debugging, programming, and production support are available. Customized solutions can further reduce costs for production testing through techniques like dedicated test modules that minimize loadboard layers and ATE instruments needed.
Efficient And Effective Test Design
Pairwise and Combinatorial testing can dramatically improve the efficiency and effectiveness of both test design (identifying and document what to test) as well as test execution (the process of executing the test cases).
This presentation, by Justin Hunter, the founder of Hexawise, to members of TISQA, explains how these methods work, highlights empirical evidence that shows this method has been proven to more than double the number of defects found per tester hour in ten separate projects, and highlights a case study of a recent user of the Hexawise test design tool.
Test
This document outlines an agenda for presenting on software testing. It discusses the importance of testing code, different types of tests like unit tests, integration tests and acceptance tests. It also introduces the PHPUnit testing framework and how to write tests in PHPUnit. Specific techniques like test doubles and test-driven development are explained. Frameworks for testing code in Zend and CakePHP are also briefly mentioned.
Overcoming The Challenges Faced in Exploratory Testing
It is pretty evident from the name ‘Exploratory Testing’, that, it is the continuous process of learning through a cycle of trial and error. Unlike scripted testing, exploratory testing does not have test cases which can be executed and compared with the results. Rather, it is an intelligent way of testing which calls for innovation and individual thought process of the tester. This is also a reason why despite automation being the big word in the modern day, exploratory testing is a hot topic.
Howto Test A Patch And Make A Difference!
1. The document provides instructions on how to test patches for Drupal modules. It outlines the patch testing process which involves a developer submitting code changes as a patch file, the patch then being reviewed and tested by others, and feedback being provided.
2. The process aims to ensure code quality through multiple reviews of changes. Anyone can help with testing regardless of skill level.
3. Testing a patch involves downloading the patch file, applying it locally, testing the functionality, then providing feedback on the issue queue page. Proper documentation of results is important.
FAQ - why does my code throw a null pointer exception - common reason #1 Rede...
A common reason for Null Pointer Exceptions in Java is a variable redeclaration instead of instantiation. Learn what that means, how to avoid it, and how to spot it, in this presentation.
Read the full blog post: http://testerhq.com/post/blogs/javafortesters/2017-08-29-faq-null-pointer-exception/
Visit my Java Web Site: http://javafortesters.com
---
# FAQ - why does my code throw a null pointer exception - common reason #1 Redeclaration
- Using `@BeforeClass` or `@Before` can setup data for use in tests
- Any 'variables' we instantiate need to be 'fields' rather than variables
- We want to instantiate them in the setup method rather than redeclare them
---
# Example of the Problem
I know I will use an `Adder` in my test so I create it as a field:
~~~~~~~~
public class WhyCodeThrowsNullPointerExceptionTest {
Adder adder;
~~~~~~~~
I don't want to re-instantiate it each time so I make an `@BeforeClass` method to instantiate it:
~~~~~~~~
@BeforeClass
public static void setupAdder(){
Adder adder = new Adder();
}
~~~~~~~~
**Warning: Error in the above code**
---
# Semantic Error
I just made a Semantic coding error. This won't be caught by a compiler, but it will cause my `@Test` to fail with a Null Pointer Exception.
In the setup method I really wanted to assign a value to the field, instead I created an new variable with the same name.
# In General
- Try to write one test at a time so that if you have a problem it is easier to identify where the problem is
- Try to write working isolated tests and then refactor to a more general solution when you need it - that way, you know it was working, so you just have to work backwards to find out what went wrong
- Try to use automated IDE refactoring rather than move code around manually
- Use the IDE syntax highlighting to help spot any issues
iOS Unit Testing
A talk about unit testing for iOS apps. Part rambling introduction to test driven development, part examples of certain types of tests for iOS, and a brief mention of writing your tests using Kiwi.
Presentation13
The document outlines seven fundamental principles of software testing:
1. Exhaustive testing is unrealistic and risk-based testing is required.
2. Defects tend to cluster in specific high-risk modules.
3. Repeated identical tests become less effective at finding bugs over time ("pesticide paradox").
4. Early testing in development cycles better identifies requirements and design issues.
5. The absence of errors in testing does not prove correctness or ensure the software meets user needs.
6. Testing approaches depend on the context and type of software.
7. These principles form the foundation of effective software testing.
Understand regression testing
Regression testing is important to ensure new software changes do not break existing functionality. Automating regression testing helps manage the large number of test cases needed and speeds up release cycles. Key aspects of managing regression include establishing a baseline, comparing new results to the baseline, debugging failures efficiently, and automating testing processes to reduce human effort and testing time.
All you need to know about regression testing | David Tzemach
All you need to know about Regression testing| David Tzemach
1. Overview
2. What is “Regression” testing…?
3. When should you use it..?
4. How to implement..?
5. Test Recommendations
6. Considerations when building Regression tests
Test Reports
The document discusses various test reporting tools that testers use such as Pareto charts, cause-effect diagrams, and check sheets. It then provides examples of eight interim test reports that provide status updates on functional testing, defects uncovered versus corrected, and average age of uncorrected defects. The summaries provide testing metrics to analyze progress and identify issues.
Testing in Django
The document discusses testing in Django and provides an overview of writing tests from an evolutionary perspective. It begins by introducing the speaker and asking attendees to raise their hands based on their testing experience. It then defines what a test is, using an example of manually testing a function in the Python interpreter. It describes how tests can evolve to be automated and integrated into Django's testing framework. Finally, it outlines four key reasons for writing tests: to fix bugs only once, enable refactoring, serve as documentation, and clarify thinking.
Unit Testing
The document introduces the JUnit testing framework and discusses how automatic unit testing can help save time by dividing testing into smaller units and providing a uniform testing tool. It explains that unit testing involves dividing code into classes or related classes, then writing test cases that specify conditions, states, and behaviors to test before and after each change is made to verify expected results. The document also outlines the three steps - arrange, act, and assert - for writing test cases to set up object snapshots, invoke methods to create changes, and check final states match expectations.
What's hot (14)
Overcoming The Challenges Faced in Exploratory Testing
Overcoming The Challenges Faced in Exploratory Testing
FAQ - why does my code throw a null pointer exception - common reason #1 Rede...
FAQ - why does my code throw a null pointer exception - common reason #1 Rede...
All you need to know about regression testing | David Tzemach
All you need to know about regression testing | David Tzemach
Similar to Final frontier testinginproduction
Principles and Practices in Continuous Deployment at Etsy
This document discusses principles and practices of continuous deployment at Etsy. It describes how Etsy moved from deploying code changes every 2-3 weeks with stressful release processes, to deploying over 30 times per day. The key principles that enabled this are innovating continuously, resolving scaling issues quickly, minimizing recovery time from failures, and prioritizing employee well-being over stressful releases. Automated testing, deployment to staging environments, dark launches, and extensive monitoring allow for frequent, low-risk deployments to production.
Software testing overview by subbu
Testing is necessary to identify correctness, completeness, and quality of software. There are various testing techniques including white box testing which tests internal logic and structure based on code coverage, and black box testing which tests functionality based on requirements without knowledge of internal design. Equivalence partitioning is a black box technique that divides inputs into equivalence classes of data expected to produce the same outputs, helping minimize the number of test cases needed. How much testing is enough depends on risk factors like potential costs of failures. Exhaustive testing testing all combinations is not feasible due to the vast number of possibilities.
Software Testing_Overview
Testing is necessary to identify correctness, completeness, and quality of software. There are various techniques for testing software such as white box testing which tests internal logic and structure, and black box testing which tests without knowledge of internal design. Equivalence partitioning divides inputs into classes to minimize the number of test cases needed. Exhaustive testing all possible combinations is not feasible due to the large number of tests required. Risk-based testing prioritizes testing based on risk to the system to determine what to test first and most thoroughly.
Review of an open source unit test tool- Cucumber_Presentation
Unit testing validates individual units or components of software to ensure they perform as designed. Cucumber is a testing framework that uses plain English scenarios in a Given-When-Then format to test software. It supports various programming languages and serves as both documentation and automated tests. Cucumber scenarios are written in feature files, while step definitions contain the actual code to implement the scenarios in code. This allows ensuring scenarios pass by writing code to implement the steps.
Configuration testing
This document discusses configuration testing and management. Configuration testing involves testing software and systems on different hardware and software combinations to check for compatibility issues. It is important because the number of possible configurations is usually too large to fully test. Configuration management is also important for tracking what is being tested and different versions. Hardware and software configuration testing both help ensure compatibility and identify issues across environments.
Testing Hourglass at Jira Frontend - by Alexey Shpakov, Sr. Developer @ Atlas...
Alexey Shpakov presents on testing in Jira Frontend. He discusses the testing pyramid with unit, integration, and end-to-end tests. He then introduces the concept of a "testing hourglass" which adds deployment and post-deployment verification to the pyramid. Key aspects of each type of test are discussed such as using feature flags, monitoring for flaky tests, and gradual rollouts to reduce risk.
Manual testing visonia
Testing software is essential to ensure it works properly and performs as intended. Various testing levels are described from unit testing of individual components to system testing of integrated modules. An overview of the software development lifecycle is provided from requirements gathering to maintenance, and key testing activities are outlined at each stage like test planning, case design, execution, and reporting. Standard documents involved in testing are also summarized such as test plans, cases, and bug reports to track issues.
Tdd dev session
This document provides an overview of test-driven development (TDD) and the use of mock objects. It defines key TDD concepts like unit tests, test fixtures, test methods, and test suites. It explains that the goal of unit tests is to test individual classes and methods in isolation. The document discusses different types of testing like functionality testing, integration testing, and system testing. It emphasizes that unit tests using mock objects are the smallest and most focused type of testing. The document outlines the TDD process of writing a test, making it fail, writing code to pass the test, refactoring code, and repeating. It explains benefits of TDD like reducing bugs and enabling safe refactoring. It also discusses principles
Application Testing
* The Testing Phase
* Testing your Web Apps
* Testing Strategies and Tactics for Mobile Applications
Myths and reality about software testing
Most of the people might say that software test engineers do not write code. Testers normally need completely different skill set which could be a mix of Java, C, Ruby, and Python.
That is not all you require to be a successful tester. A tester requires having a good knowledge of the software manuals and automation tools.
Depending on the complexity of a project, a software testing engineer may write more complicated code than the developer.
ANTIVIRUS
The document summarizes the results of a performance test of 21 antivirus and internet security products on a Windows 8.1 system. The test measured the impact of the security software on common tasks like file copying and downloading. It found that suite products have a higher impact than antivirus-only products due to running more background processes. The test used standard tools to ensure accurate and replicable results. Overall system performance is also affected by factors like hardware specifications, having unnecessary programs running, and failing to keep software up to date.
5-Ways-to-Revolutionize-Your-Software-Testing
This document provides 5 insights to revolutionize software testing: 1) There are two types of code (experience and infrastructure) that require different testing approaches; 2) Testing should focus on capabilities rather than features; 3) Focus on testing techniques rather than individual test cases; 4) Testing should improve development rather than just find bugs; 5) Testing needs innovation to engage talent and avoid repetitive work. The author advocates shifting testing strategy to higher levels of abstraction and partnering with development to build quality in from the start.
Software Testing basics
This document provides an overview of software product testing, including roles and responsibilities, development cycles, testing cycles, definitions, artifacts, tools, levels of testing, methods, techniques and types of testing. It discusses the role of testers and developers. It also includes descriptions of various testing documents, tools, levels of testing including unit, integration, system and acceptance. Different testing methods like black box, white box and gray box testing are defined. Various testing types such as load testing, security testing, compatibility testing are also outlined.
Test plan
The document describes a test plan for a Waste Management Inspection Tracking System (WMITS) software. It includes:
1. An overview of what must be included in a test plan such as the test specification, test procedures for unit, integration, and validation testing.
2. A case study of testing the WMITS software requirements specification, which aims to automate waste management inspections and minimize time/paperwork.
3. Details of the testing strategy including unit testing of individual modules, integration testing by running the software at the client's location, and validation testing to verify requirements.
Deviceanywhere studio 5.1
This Content is just replica of Deviceanywhere Studio 5.1
User Manual.
All Rights reserved with Deviceanywhere Studio.
Copyright © 2013 Keynote Systems, Inc. All rights reserved.
Test execution may_04_2006
The document discusses test execution and reporting. It provides details on general test procedures including planning, execution, and evaluation. It describes preparing the test infrastructure by setting up systems, software, and standards. Test execution involves conducting individual test cases, verifying results against expected outcomes, and analyzing any variances. Reporting includes documenting test logs, creating incident reports for problems, and providing effective defect reports using a standardized template. Defects are then resolved by referring them to defect or change management processes.
TEST EXECUTION AND REPORTING
The document discusses test execution and reporting. It provides details on general test procedures including planning, execution, and evaluation. It describes preparing the test infrastructure by setting up systems, software, and standards. Test execution involves conducting individual test cases, verifying results against expected outcomes, and analyzing any variances. Reporting includes documenting test logs, creating incident reports for problems, and providing effective defect reports using a standardized template. Defects are then resolved by referring them to defect or change management processes.
Testing Presentation
The document provides an overview of manual software testing concepts and processes. It discusses why testing is important, the different levels of testing (unit, integration, system acceptance), test planning including test cases and test data preparation, defect reporting, and test tracking and reporting. The software development lifecycle of requirements, design, coding, testing, release and maintenance is also summarized.
Future of QA
The document discusses predictions for the future of testing and QA. It predicts that test automation will significantly increase from 31% currently to become a major part of the QA process. It also predicts that testing responsibilities will move earlier in the development cycle, with more testing by developers and end users. Requirements testing will also improve with automation and new technologies that provide 100% test coverage and automatically generate test cases.
Futureofqa
The document discusses predictions for the future of testing and QA. It predicts that test automation will significantly increase from 31% currently to become a major part of the QA process. It also predicts that testing responsibilities will move earlier in the development cycle, with more testing by developers and end users. Requirements testing will also improve with automation and new technologies that provide 100% test coverage and automatically generate test cases.
Similar to Final frontier testinginproduction (20)
Principles and Practices in Continuous Deployment at Etsy
Principles and Practices in Continuous Deployment at Etsy
Review of an open source unit test tool- Cucumber_Presentation
Review of an open source unit test tool- Cucumber_Presentation
Testing Hourglass at Jira Frontend - by Alexey Shpakov, Sr. Developer @ Atlas...
Testing Hourglass at Jira Frontend - by Alexey Shpakov, Sr. Developer @ Atlas...
Recently uploaded
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
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.
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
“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.Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
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
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Webinar: Designing a schema for a Data Warehouse
Are you new to data warehouses (DWH)? Do you need to check whether your data warehouse follows the best practices for a good design? In both cases, this webinar is for you.
A data warehouse is a central relational database that contains all measurements about a business or an organisation. This data comes from a variety of heterogeneous data sources, which includes databases of any type that back the applications used by the company, data files exported by some applications, or APIs provided by internal or external services.
But designing a data warehouse correctly is a hard task, which requires gathering information about the business processes that need to be analysed in the first place. These processes must be translated into so-called star schemas, which means, denormalised databases where each table represents a dimension or facts.
We will discuss these topics:
- How to gather information about a business;
- Understanding dictionaries and how to identify business entities;
- Dimensions and facts;
- Setting a table granularity;
- Types of facts;
- Types of dimensions;
- Snowflakes and how to avoid them;
- Expanding existing dimensions and facts.
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Recently uploaded (20)
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
WeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation Techniques
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
GraphRAG for Life Science to increase LLM accuracy
GraphRAG for Life Science to increase LLM accuracy
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdf
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Final frontier testinginproduction
- 1. The Final Frontier? Testing in Production Franziska Haaf (@franziskaHaaf) Benjamin Hofmann (@benny_hfm) Marcel Gehlen (@Marcel_Gehlen)
- 2. Why should I test in Production? How do others test in Production already? What to do to tackle common contraints? How do I start testing in Production? Starring...
- 3. Who has ever found a bug in production?
- 4. Who has ever found a bug in production? Who found a bug in production more than once?
- 5. Who has ever found a bug in production? Who found a bug in production more than once? Who found a bug in production they could only find or reproduce in Production?
- 6. A staging environment is designed to duplicate production so you can test your software in a production-like environment to prohibit bugs from occuring in your actual Production.
- 7. We invest a lot of time and money in our staging environment: We need additional production- grade hardware and more software licences. We have aditional maintenance costs for patches or updates.
- 9. Different Hardware Different Server Setup Different Software Versions Different Application Different neighboring Systems A staging environment is never a Duplication of Production
- 10. You and your users have the same patch levels You have the best test data available Your neihboring systems are (almost) never down Every problem you find is a problem your users are facing right now There is a place where...
- 13. Give your software to a group of end users and have them interact with it. Then watch what they do and listen to their feedback.
- 14. Give your software to a group of end users and have them interact with it. Then watch what they do and listen to their feedback: Dogfooding Beta-Testing A/B-Testing
- 15. „Sufficiently Advanced Monitoring is indistinguishable from Testing.“ - Ed Keys, Google, 2009
- 18. attempted logins successful logins 1 hour
- 19. 1 hour calls to /login attempted logins successful logins
- 20. calls to /login attempted logins successful logins 2 days
- 21. Production starts with the deployment. So this is where we should start testing! Canary Release Staged Rollout Dark Launch
- 22. Dark Launch
- 23. Dark Launch
- 24. Dark Launch !
- 26. Deployed means the new code has been put on Production. Released means the new code is affecting end users.
- 29. Alert! Condition: Red! I can‘t possibly test in Production!
- 31. If I can use a Feature in Production then so can the user!
- 33. if(isTestUser()) { newFeature(); } else { oldFeature(); } Feature Toggle
- 34. Feature Toggle
- 35. Feature Toggle
- 37. I will break our Production!
- 39. Adopt technical resilience Breaking Production
- 40. Adopt technical resilience Adopt business resilience Breaking Production
- 41. Adopt technical resilience Adopt business resilience Alert on your Monitoring Breaking Production
- 42. Adopt technical resilience Adopt business resilience Alert on your Monitoring Breaking Production Reduce mean time to repair
- 44. My test data will screw up our analytics!
- 45. Analytics
- 47. Evaluate statistical significance Flag / Seperate test data Analytics
- 48. Evaluate statistical significance Flag / Seperate test data Use feature toggles Analytics
- 50. If we expose Endpoints for testing in Production we can be hacked!
- 51. Security Risks
- 52. Hide features behind an authentication layer Security Risks
- 53. Hide features behind an authentication layer Make features only accessible via VPN / Proxy Security Risks
- 54. Hide features behind an authentication layer Make features only accessible via VPN / Proxy Transparency: Logging, Monitoring, Tracing Security Risks
- 56. Get into the right mindset Pick one(!) thing to move forward Find out what you are already doing Widen your activities at a steady rate Pick a new thing How to move testing to Production
- 57. Alert! Condition: Red! Testing in Production is a huge risk!
- 58. If only there was a way to know about risk ...
- 59. Test It!
- 60. „F}}k Staging, Test in Production.“ Charity Majors, Honeycomb.io, 2018
- 61. Credits Speakers Benjamin Hofmann (@benny_hfm) Marcel Gehlen (@Marcel_Gehlen) Artwork Franziska Haaf (@franziskaHaaf)