-
The UoNAfyaApp360 Daktari app runs on Flutter version 3.3.8 stable channel. To check the flutter version and channel installed in your machine run
flutter --version
. -
To switch from another channel of Flutter to the stable channel run
flutter channel stable
. -
To install Flutter version 3.3.8 run
flutter version v3.3.8
.
Looks like we are done with the prerequisites :-)
- Clone the project by running
git clone [email protected]:savannahghi/pro_health_360_daktari.git
or download the code cd pro_health_360_daktari
- Run
flutter pub get
- You can now run the app on an attached device or emulator
To run unit and widget tests, you will require to install lcov
by running sudo apt-get install lcov
in the terminal. Finally, run the following commands in the terminal:
-
From the root folder, run
flutter test --coverage test/
-
Run
genhtml -o coverage coverage/lcov.info
-
To view the coverage, open the html file generated at
coverage/index.html
with your preferred browser.
To run integration tests, ensure that you have an emulator running. See instructions on how to run an emulator.
- Then run
flutter drive --target=test_driver/app.dart
- Dart 2: >= 2.12
- Flutter: >=2.2.3
First off, thanks for taking the time to contribute!
Be sure to check out detailed instructions on how to contribute to this project here and go through out Code of Conduct.
GPG Signing: As a contributor, you need to sign your commits. For more details check here
This library is distributed under the MIT license found in the LICENSE file.
In order for you to run the application locally on your machine, you will need the following environment variables
- PROD_SENTRY_DNS and DEV_SENTRY_DNS that will be used to send error messages to your Sentry error reporting server
- DEV_STREAM_API_KEY, DEMO_STREAM_API_KEY and PROD_STREAM_API_KEY that will be used to enable you to connect to the GetStream API
If you want to add an environment variable to CI, you will need to run the following command to encode the ENV file into a string format. The --b 0
will prevent the new lines from being encoded
base64 --b 0 --i .env
In the CI configuration, you can decode the string into the ENV variable using this command which will decode the string into the ENV file
echo $ENCODED_APP_ENV | base64 --decode > .env