SWE - FINAL EXAM | 2026 UPDATE | QUESTIONS AND ANSWERS | 100%
CORRECT
Why is it important not to work in master? - -Working on master can corrupt if you leave
unfinished code and can also open up to introducing regressions to the code base. Also
makes it difficult to undo things you added and want to remove.
--What is the git command to create a new branch? - -git branch {branchName}
--What is the git command to checkout a branch? - -git checkout {branchName}
--What is the git command to create and checkout a branch at the same time? - -git
checkout -b branchName
--Can you have many different branches at the same time? - -Yes, it is encouraged as good
practice. Allows multiple teams to work on different features at a time.
--When you open a Pull Request, what do you expect someone on your team to do? - -You
expect them to review your code, leave comments and create a discussion. Also expect
them to either deny or accept the request.
--If your code is "red", meaning some of the tests failed in continuous integration, should
you merge it? - -No, you should check it and redo until the tests are passed.
--Code Review = _____________ + Code - -Discussion
--What are some of the things that code reviewers should look for? - -Test Coverage
Missing Test Cases
Check for Company Style
Judge Readbility
If Code can be Refactored
--What are some of the benefits of code review? - -Gives a second pair of eyes and helps
give confidence to the developer.
Helps the reviewer get a better understanding of the code base.
--How does continuous integration help maintain a stable master branch? - -Checks if the
application passes the test suite without introducing any regressions. Runs automatically
whenever new code is checked in.
--Why should we use continuous integration? - -Ensures that high quality code is always
being produced and that no regressions are being introduced to the code base.
, Also lets you know if the program will work in different environments as the tests are run in
an independent environment.
--What is continuous deployment? - -A workflow where changes are run through CI
automatically and pushed to github. This automates the deployment process.
--What is it called when new code breaks old code? - -A regression
--What is a test suite? - -Collection of tests which ensures that your program works as
intended.
--What are some of the benefits of automated testing? - -Automated tests save time and
money as they catch more bugs and at a faster than humans, reducing the amount of
manpower needed.
Allows developers to continue working without leaving editor.
--Why are QA teams not a replacement for good testing practices? - -Expensive and cannot
catch as many mistakes or run as many tests as a machine could do automatically.
--How does good testing practices enable confidence? - -Good testing practices gives
developers confidence to introduce large changes without fear of introducing regressions as
the tests would notify them.
--How does a test suite serve as living documentation? - -Test suites, unlike comments,
never go out of date as they constantly need to be updated to test new additions.
As every test covers pieces of the app, it is easy to go to the test itself to determine what a
piece of the app should do and if it functions properly.
--Where do you go if you are unsure of how an applications supposed to work? - -The test
suite as it tells you what the expected behavior should be and what is wrong.
--What is the best way to achieve confidence in a growing code-base? - -Automated tests
--How do we amplify that confidence and achieve bigger wins in time savings and code? - -
Use Test Driven Development, which is a process that drives the design and development of
an app through tests.
--What are the three steps to TDD? - -Red, Green, Refactor
--What happens at the "Red" step? - -Write tests that covers the behavior you want to see.
The test should fail but will let you know what you need to do.
--What happens at the "Green" step? - -Read and attempt to understand why the test is
failing.
Write as little code as possible to pass the test.
CORRECT
Why is it important not to work in master? - -Working on master can corrupt if you leave
unfinished code and can also open up to introducing regressions to the code base. Also
makes it difficult to undo things you added and want to remove.
--What is the git command to create a new branch? - -git branch {branchName}
--What is the git command to checkout a branch? - -git checkout {branchName}
--What is the git command to create and checkout a branch at the same time? - -git
checkout -b branchName
--Can you have many different branches at the same time? - -Yes, it is encouraged as good
practice. Allows multiple teams to work on different features at a time.
--When you open a Pull Request, what do you expect someone on your team to do? - -You
expect them to review your code, leave comments and create a discussion. Also expect
them to either deny or accept the request.
--If your code is "red", meaning some of the tests failed in continuous integration, should
you merge it? - -No, you should check it and redo until the tests are passed.
--Code Review = _____________ + Code - -Discussion
--What are some of the things that code reviewers should look for? - -Test Coverage
Missing Test Cases
Check for Company Style
Judge Readbility
If Code can be Refactored
--What are some of the benefits of code review? - -Gives a second pair of eyes and helps
give confidence to the developer.
Helps the reviewer get a better understanding of the code base.
--How does continuous integration help maintain a stable master branch? - -Checks if the
application passes the test suite without introducing any regressions. Runs automatically
whenever new code is checked in.
--Why should we use continuous integration? - -Ensures that high quality code is always
being produced and that no regressions are being introduced to the code base.
, Also lets you know if the program will work in different environments as the tests are run in
an independent environment.
--What is continuous deployment? - -A workflow where changes are run through CI
automatically and pushed to github. This automates the deployment process.
--What is it called when new code breaks old code? - -A regression
--What is a test suite? - -Collection of tests which ensures that your program works as
intended.
--What are some of the benefits of automated testing? - -Automated tests save time and
money as they catch more bugs and at a faster than humans, reducing the amount of
manpower needed.
Allows developers to continue working without leaving editor.
--Why are QA teams not a replacement for good testing practices? - -Expensive and cannot
catch as many mistakes or run as many tests as a machine could do automatically.
--How does good testing practices enable confidence? - -Good testing practices gives
developers confidence to introduce large changes without fear of introducing regressions as
the tests would notify them.
--How does a test suite serve as living documentation? - -Test suites, unlike comments,
never go out of date as they constantly need to be updated to test new additions.
As every test covers pieces of the app, it is easy to go to the test itself to determine what a
piece of the app should do and if it functions properly.
--Where do you go if you are unsure of how an applications supposed to work? - -The test
suite as it tells you what the expected behavior should be and what is wrong.
--What is the best way to achieve confidence in a growing code-base? - -Automated tests
--How do we amplify that confidence and achieve bigger wins in time savings and code? - -
Use Test Driven Development, which is a process that drives the design and development of
an app through tests.
--What are the three steps to TDD? - -Red, Green, Refactor
--What happens at the "Red" step? - -Write tests that covers the behavior you want to see.
The test should fail but will let you know what you need to do.
--What happens at the "Green" step? - -Read and attempt to understand why the test is
failing.
Write as little code as possible to pass the test.
