Week #4

Week #4 #

Testing and QA #

For the quality assurance, we made an automated build for our project that is activated on each push.

Evidence of test execution #

The pipeline

CI/CD #

Tools we used #

Challanges #

  • Making an automated build for the Gamemaker project was quite hard and demanded a lot of time

Deployment #

Staging #

Each push is going through the build pipeline, so if is not successful, we would not authorise the merge requests.

Production #

Release builds meant for publishing are compiled on our developer’s machine locally for now. This is to ensure optimal build settings.

Vibe Check #

  • We still have some problems with organisation and the general mood of the team
  • Some people are not satisfied with their roles and the need to make something creative under the deadlines, so we need to create a more comfortable environment
  • Some members are still not present with a legal reason, so the communication is not as good as it could have been

Weekly commitments #

Individual contribution of each participant #

Plan for Next Week #

Things to code #

  • put the second level together

Narrative and level design #

  • formulate the level design for the second level
  • finish writing the second level dialogues

Visual Design #

  • make the backgrounds for the next scenes
  • design objects for interaction
  • animate objects for interaction

Organisation #

  • group call to discuss the process
  • keep consistent chat communication

Confirmation of the code’s operability #

We confirm that the code in the main branch:

  • In working condition.
  • Run via docker-compose (or another alternative described in the README.md).