Our Workflow Overview - Jacob1225/pufferfish-minecraft-mod GitHub Wiki

Our team works with the Scrum Agile Framework in mind. Thus, we are constantly incorporating new user stories into features at all times of the development.

The general workflow is depicted below:

Link to original link: https://drive.google.com/file/d/1XQZ9zKM5UhAmLkOD_nkZAhkEnB7zxpCT/view?usp=sharing

Stage 1: Our team uses Google Drive for sharing, discussing, and jotting down ideas. This is where user stories and ideas are created.

Stage 2: User stories are broken down into more specific tasks and added to Jira which will facilitate task assignment and progress tracking.

Stage 3: Eclipse and IntelliJ are used by the developers, who then push code to GitHub where we go through our GitHub protocols for branching, code review, pull requests, and merging.

Stage 4: Testers have implemented MCJunitLib and a CircleCI workflow with various test coverage. Automated testing lets developers know when their code is okay to merge with the main branch.

Stage 5: A feature is ready when it is successfully merged to the main branch. The task can be marked as done on Jira and linked to the appropriate pull request for easy tracking. The whole process is continuous and every feature goes through this general workflow.

Each area has been discussed in more depth in the other Wiki pages (particularly in the Implementation section) and by reviewing them, it is clear how our team connects each element and step of development with one another. We use a combination of many different tools and they all work together to create a cohesive development environment.

Overview of the how the testing fits in our workflow: