Flutter test. Batch tests. Badges.

.github/workflows/flutter_test.yml

@@ -0,0 +1,28 @@
+
+name: Flutter Unit Tests
+
+on:
+  pull_request:
+
+jobs:
+  tests:
+
+    permissions:
+      # For actions/checkout to fetch code
+      contents: read
+      # For github/codeql-action/upload-sarif to upload SARIF results
+      security-events: write
+      # Only required for a private repository by github/codeql-action/upload-sarif to get the Action run status
+      actions: read
+
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Check out code
+        uses: actions/checkout@v1
+
+      - name: Setup Flutter
+        uses: subosito/flutter-action@v1
+
+      - name: Run Flutter Tests
+        run: flutter test

README.md

@@ -1,4 +1,6 @@
 # Angeleno - Profile
+<a href="https://github.com/CityOfLosAngeles/angeleno-my-account-flutter/actions"><img src="https://github.com/CityOfLosAngeles/angeleno-my-account-flutter/workflows/Dart%20Analyzer/badge.svg" alt="Dart Analyzer Status"></a>
+<a href="https://github.com/CityOfLosAngeles/angeleno-my-account-flutter/actions"><img src="https://github.com/CityOfLosAngeles/angeleno-my-account-flutter/workflows/Flutter%20Unit%20Tests/badge.svg" alt="Flutter Tests Status"></a>
 
 ## Getting Started
 This branch should act as our main branch until we have a working Minimum Viable Product (MVP) to merge into the `main` branch. To start development you'll `git clone` this repo; after cloning you'll by default be on the main branch, but you can `git checkout mvp-skeleton` to switch to the branch with the code being worked on. From the `mvp-skeleton` branch, you can branch off to work on your own work/issue by running `git checkout -b your-branch-name`. When opening the pull request for your work, make sure the branch is being merged into `mvp-skeleton` and not `main`.

tests.bat

@@ -0,0 +1,8 @@
+@echo off
+
+call echo Running flutter tests
+call flutter test
+
+call echo Running dart analyze
+call dart analyze
+