Scribd
Upload
7 views2 pages

Chapter10 (Se305)

Uploaded by

T O K
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
7 views2 pages

Chapter10 (Se305)

Uploaded by

T O K
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Our Development and QA teams test new features in environments like our real system.

If testing
only happens a few times a year, developers may discover mistakes months later, making xes
harder and reducing learning. We should work together early to catch issues and improve our
code.

Q: Why is automated testing important?


A: Automated testing is important because it saves time and money as code grows.
Without it, testing becomes too hard to manage for tech companies.

Q: How does continuously building, testing, and integrating our code and
environments improve software quality?
• Automated Tests: Ensures quality from the start.
• Fast Feedback: Helps x problems early.
• Reduces errors.
• Deployment Pipeline: Tests code in a production-like environment.
• Quick Error Detection
• Simpli es work ows with tools like GitHub Actions.

Q: Why is it important to continuously build, test, and integrate our code and
environments?
• Always Running: The build and test processes can work all the time, no matter when
people are working.
• Know What’s Needed: We can see all the parts needed to make and test the code.
• Easy Installation: We can package our applications for easy installation.
• Use Containers: We can put our apps in containers to make them easier to deploy.
• We can create environments that are like the real one every time.

Q: What is the process of continuously building, testing, and integrating our code
and environments?
• We start the deployment pipeline with the commit stage, where we build and package
the software, run automated tests, and check for issues like duplication.
• If successful, we move to the acceptance stage, which deploys the packages into a
production-like environment and runs acceptance tests.
• Once accepted into version control, we package our code once to ensure consistency
throughout the pipeline depolyment.
• This method lets us deploy in staging and test environments like in production, making it
easier to nd and x mistakes. Staging simulates the real setup.

Q: What is a deployment pipeline?


A: A deployment pipeline is a system that helps move new code and updates from where
it's created to users quickly and accurately. It is an important part of DevOps, Continuous
Integration, and Continuous Delivery. The main goal is to get software to users as fast and
smoothly as possible, and it usually has three stages: Development, Test, and Production.
fi
fi
fl
fi
fi
fi
Q: How can we build a fast and reliable automated validation test suite to ensure our
code remains in a deployable state?
A: To keep our code ready to use and nd problems quickly, we need fast automated tests
that run whenever we make changes. There are three types of tests, from fastest to
slowest:
• Unit Tests: These check a single method, class, or function to make sure it works as the
developer wanted.
• Acceptance Tests: Make sure the application meets business goals and has no new
errors.
• Integration Tests: Test if the application works well with other programs using real
connections.

Q: Why is it important to catch errors early in our automated testing?


• It helps nd problems early in the testing phase.
• Fast Tests First: We run fast automated tests before slower ones and manual testing.
• Focus on Unit Tests: Most errors should be caught with unit tests for quicker feedback.
• Reduce Delays

Q: What does it mean to pull our Andon cord when the deployment pipeline breaks?
A: Pulling our Andon cord means stopping new work when the deployment pipeline has
issues

In this chapter, we set up automated tests to ensure our build is always in a good, deployable
state. We organized our testing into a deployment pipeline and created a culture where everyone
helps x problems quickly if tests fail.This prepares us for continuous integration, allowing small
teams to safely develop, test, and deploy code, which delivers value to customers.
fi
fi
fi

You might also like