This build will always fail because it has two examples of failing tests: one based on the source code, and one based on an incorrect test. The status badge is here just to demonstrate continuous integration (CI) via GitHub Actions.

Collaborate with your classmates on a conceptual level but do not share code. Submit individually.

• Simple hello world example
• Get started with Git source code management
• Make sure you can access the course examples on GitHub
• Verify that you have a working development environment
• Make sure you can use your development environment to modify and update your projects on GitHub
• Use the Maven command-line build tool for Java
• Understand the basics of Test-Driven Development (TDD)
• Use JUnit for automated unit testing in Java
• Continuous integration with Travis

These are one-time steps:

1. Create a GitHub account (if you do not have one already).

2. Request the GitHub Student Developer Pack using your official Loyola email address (optional).

In this section, you will perform one or more iterations of the (more frequent) inner circle involving

1. Accept the GitHub Classroom invite provided to you in Sakai.

2. Work on the project following this GitHub-based workflow except the "repository import" section, which GitHub Classroom already took care of:

   • edit the source code
   • compile the source code to executable code
   • test (or run) the executable code
   • frequently commit and push your local modifications to your remote GitHub Classroom repository

When your project is ready to grade, submit your complete GitHub Classroom repository URL including your GitHub userid on Sakai as an inline submission.

Total 3.5 points:

• (1 point) submission of your GitHub repo's URL via Sakai (your repo should still show original project commit history - this automatically happens when you import this repo)
• (0.5 point) leave project structure intact
• (1 point) fix or remove the erroneous test(s)
• (1 point) make the other test(s) pass without modifying anything else in src/test

To clarify, your submitted repo must include at least one commit that you made and pushed up to the GitHub server.