GitHub Actions and Jest Testing CI/CD Setup Project Overview This project demonstrates how to set up a Continuous Integration/Continuous Deployment (CI/CD) pipeline using GitHub Actions and Jest testing. By integrating these tools, I automated the process of running unit tests on my JavaScript project every time changes are pushed to my GitHub repository. This setup ensures that my code is always tested and provides feedback on the success or failure of my changes in real-time.

Why It Matters Automating testing with CI/CD tools like GitHub Actions improves the development workflow by:

Ensuring consistency: Every change gets tested automatically. Saving time: Reduces the need to manually run tests after every change. Preventing bugs: Automatically catches errors early in the development process. This setup is beneficial for developers aiming to maintain high code quality and reduce manual intervention in testing.

Steps to Set Up GitHub Actions and Jest Testing

1. Install GitHub CLI Before starting with the project, make sure to install the GitHub CLI to interact with your repositories directly from the terminal.

Run the following command to check if GitHub CLI is installed: bash Copy code gh --version If not installed, follow the installation guide at cli.github.com. 2. Authenticate GitHub CLI Once the GitHub CLI is installed, authenticate it with your GitHub account by running:

bash Copy code gh auth login Follow the prompts to authenticate via your Personal Access Token (PAT).

3. Create a New GitHub Repository Create a new GitHub repository to store your project code. You can also use an existing repository if you prefer.

bash Copy code gh repo create --public gh repo clone / cd 4. Set Up Your JavaScript Project In this project, I used Jest, a testing framework, to ensure that my code functions as expected. Here's how you can set it up:

Initialize the project with npm:

bash Copy code npm init -y Install Jest as a development dependency:

bash Copy code npm install jest --save-dev Create a test folder and add an example test:

bash Copy code mkdir tests touch tests/example.test.js Add a simple Jest test in tests/example.test.js:

javascript Copy code test('adds 1 + 2 to equal 3', () => { expect(1 + 2).toBe(3); }); Run the test locally:

bash Copy code npx jest 5. Commit and Push Your Code to GitHub Once Jest is set up and your test is working, commit the changes to your GitHub repository.

bash Copy code git add . git commit -m "Initial project setup" git push -u origin main 6. Set Up GitHub Actions Workflow To automate the testing process, set up a GitHub Actions workflow. Create the necessary folders and YAML file to define the workflow.

Create the workflow directory and YAML file:

bash Copy code mkdir -p .github/workflows touch .github/workflows/ci.yml Add the following content to ci.yml:

yaml Copy code name: Jest CI

on: push: branches: [main]

jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v2 - name: Setup Node.js uses: actions/setup-node@v2 with: node-version: '16' - run: npm install - run: npm test Commit and push the workflow file to GitHub: bash Copy code git add .github/workflows/ci.yml git commit -m "Add CI workflow" git push 7. Test the Workflow To ensure that everything is working, make a small change to your project and push it to GitHub. The GitHub Actions workflow should trigger and run the tests.

bash Copy code echo "// Test change" >> index.js git add . git commit -m "Test workflow" git push Check the GitHub Actions tab to view the status of your tests.

8. Document the Process Finally, update your README.md file with detailed instructions on setting up the GitHub CLI, configuring the GitHub Actions workflow, and running the tests. Include screenshots of the GitHub Actions logs and console output for test results.

Results By following these steps, I was able to successfully set up automated testing for my project. Now, every time I make a change and push it to GitHub, the tests are automatically run, providing me with real-time feedback on the success or failure of my code.

This process ensures that I catch errors early and maintain the integrity of my code. I've also included detailed instructions and screenshots to help you replicate this setup.

Challenges and Solutions One of the main challenges I faced was ensuring the YAML file was correctly formatted. YAML is sensitive to indentation, and a small mistake can cause the workflow to fail. After testing different configurations and reviewing documentation, I successfully got the tests running with the Jest testing framework.

Screenshots GitHub Actions Log 

Console Output 

Call to Action Feel free to explore the full project on my GitHub repository. Clone the repository, set up the CI/CD workflow, and experiment with running Jest tests automatically whenever you make changes to the code.

You can find the project here.

Contributing Contributions are welcome! If you have suggestions or improvements for this setup, feel free to open an issue or submit a pull request.

License This project is open-source and available under the MIT License.