GitAuto: Add a GitHub Actions workflow to automatically conduct flutter test

[gitauto-for-dev]

Resolves #8

Why is this feature needed?

This feature is needed to ensure that every change and new feature added to the repository is automatically tested using Flutter's testing framework. Automating tests on pull requests and pushes helps us to catch issues early, improve code quality, and maintain project stability.

What and how are we changing? Why this approach?

We are adding a GitHub Actions workflow file (".github/workflows/flutter_test.yml") to automatically run Flutter tests under the following conditions:

• When a pull request is created targeting the default branch (master).
• When there is a push to any branch other than the default branch.
• When the workflow is triggered manually.

This approach leverages GitHub Actions and existing Flutter-related actions to set up the environment and run tests, ensuring consistency and reliability without manual intervention.

What actions are required from users?

No immediate actions are required from users. However, it is recommended to:

• Ensure that new code changes include tests if applicable.
• Monitor GitHub Actions for test results to review potential issues early in the development process.
• Manually trigger the workflow if needed using the "Workflow Dispatch" option provided in GitHub Actions.

How does it work? (Technical details)

The workflow is defined in a new YAML file under the ".github/workflows/" directory. Key technical details include:

• The workflow is triggered on:
  • Push events to all branches except "master".
  • Pull request events that target the "master" branch.
  • Manual triggers through the workflow dispatch event.
• The job named "test" runs on an Ubuntu latest virtual machine.
• The steps executed include:
  • Checking out the repository using the official checkout action.
  • Installing a specific version of Flutter (3.7.0) via the subosito/flutter-action.
  • Running the Flutter tests by invoking the "flutter test" command.
    This configuration ensures that tests are run in an isolated environment consistent with local development setups.

Is it backwards compatible?

Yes, this change is backwards compatible. It only adds a new workflow for automated testing and does not modify any existing code or functionality in the project.

Any other considerations?

• Future developments might require updating the Flutter version or adding additional steps to the workflow as the project evolves.
• It is important to ensure that the repository's "master" branch is consistently kept in sync with the testing guidelines, as this workflow is tailored for that branch.
• Feedback on the workflow behavior is welcome to further refine and optimize the testing process over time.

git fetch origin
git checkout gitauto-wes/issue-8-20250213-161015
git pull origin gitauto-wes/issue-8-20250213-161015

[gitauto-for-dev]

Committed the Check Run test error fix! Running it again...