**Course Title:** Continuous Integration and Continuous Deployment (CI/CD) **Section Title:** Automated Testing in CI/CD **Topic:** Implement automated tests in a CI pipeline and configure test reporting. (Lab topic) **Overview:** In this lab, you will learn how to implement automated tests in a CI pipeline and configure test reporting. Automated testing is an essential part of the CI/CD pipeline, as it ensures that your code is tested thoroughly before it is deployed to production. You will learn how to integrate your automated tests with a CI pipeline and configure test reporting to get insights into your test results. **Objective:** * Learn how to integrate automated tests with a CI pipeline * Understand how to configure test reporting in a CI pipeline * Implement automated tests in a CI pipeline using a sample project * Configure test reporting using a CI tool **Lab Environment:** We will use GitHub Actions as our CI tool and a sample Node.js project for this lab. You can use any other CI tool and programming language of your choice. **Step 1: Create a Sample Project** Create a new Node.js project using npm. You can use a sample project or create a new one. For this lab, we will use a simple calculator application. Create a new file called `calculator.js` and add the following code: ```javascript function add(x, y) { return x + y; } function subtract(x, y) { return x - y; } function multiply(x, y) { return x * y; } function divide(x, y) { if (y === 0) { throw new Error('Division by zero'); } return x / y; } module.exports = { add, subtract, multiply, divide }; ``` **Step 2: Write Automated Tests** Create a new file called `calculator.test.js` and add the following code: ```javascript const { add, subtract, multiply, divide } = require('./calculator'); describe('Calculator', () => { it('adds two numbers', () => { expect(add(2, 2)).toBe(4); }); it('subtracts two numbers', () => { expect(subtract(4, 2)).toBe(2); }); it('multiplies two numbers', () => { expect(multiply(4, 2)).toBe(8); }); it('divides two numbers', () => { expect(divide(8, 2)).toBe(4); }); it('throws an error when dividing by zero', () => { expect(() => divide(8, 0)).toThrowError('Division by zero'); }); }); ``` **Step 3: Configure the CI Pipeline** Create a new file called `.github/workflows/ci.yml` and add the following code: ```yaml name: CI on: [push] jobs: build-and-test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Setup node.js uses: actions/setup-node@v1 with: node-version: '14' - name: Install dependencies run: npm install - name: Run automated tests run: npm test - name: Upload test results uses: actions/upload-artifact@v1 with: name: test-results path: test-results ``` **Step 4: Configure Test Reporting** To configure test reporting, you can use a CI tool like GitHub Actions to upload your test results to a reporting tool like TestRail or Allure. For this lab, we will use GitHub Actions to upload our test results to GitHub. Add the following code to your `.github/workflows/ci.yml` file: ```yaml - name: Upload test results to GitHub uses: actions/upload-artifact@v1 with: name: test-results path: test-results env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} ``` **Conclusion:** In this lab, you learned how to implement automated tests in a CI pipeline and configure test reporting using GitHub Actions. You created a sample project, wrote automated tests, configured the CI pipeline, and configured test reporting. **Takeaways:** * Integrate automated tests with a CI pipeline to ensure that your code is tested thoroughly before it is deployed to production. * Use a CI tool like GitHub Actions to automate your testing process. * Configure test reporting to get insights into your test results. **Additional Resources:** * GitHub Actions Documentation: https://docs.github.com/en/actions * TestRail Documentation: https://www.gurock.com/testrail/docs/ * Allure Documentation: https://docs.qameta.io/allure/ **What's Next:** In the next topic, we will cover "Understanding the Differences between Delivery and Deployment" from the Continuous Delivery vs. Continuous Deployment section. **Leave a comment or ask for help if you have any questions or need further clarification on any of the topics covered in this lab.