decision_maker (Pocket Poll) - Simple Group Event Planner
https://github.com/SCCapstone/decision_maker
1 Technologies 1 Technologies
This application leverages several technologies. At a high level, it uses Flutter for the front end and Java for the back end.
1.1 Front End Technologies
For the front end we are using Flutter. In order to develop, build, and run our Flutter application, you will need to download several things: The application depends on the several external packages. Before building, one needs to fetch these by running flutter pub get (more info in section 2). Flutter Plugin and Dart Plugin will be needed for development. To install these, start android studio, go to File -> Settings -> Plugins, select the 'Marketplace' tab, select the Flutter plugin and click 'Install', click 'Yes' when prompted to install the Dart plugin, and finally click 'Restart' when prompted. 1.2 Back End Technologies
For the back end we are using Java. In order to develop, build, and run our java code, you will need to download several things: You need to make sure you have your JAVA_HOME environment variable pointing to your jdk11 location.
You will also need to add the unpacked maven bin location to you PATH environment variable.2 Running the application 2 Running the application
This section is only for building and/or running our front end application on an Android device or emulator. The following assumes the back end has been properly deployed as depicted in section 3.
There are known issues with push notifications in Android emulators. If you are experiencing any issues please try using a real android device.
If using a real Android device, you cannot use a debug apk; you must use a release apk. Inversely, if using an Android emulator you must use a debug apk, not a release one.
2.1 Compiling and Running the application from the command line
To run the application from the command line, one must: Have an android device or emulator connected to the computer.
cd into the front_end_pocket_poll directory.
Run flutter doctor to ensure build environment and system requirements are met. If they are not met, follow the instruction to resolve issues.
If no issues are found, run the command flutter run to build, install, and run the application on the connected device/emulator. 2.2 Compiling and Running the application from Android Studio
Note this will build a debug-apk on your device. To run the application from Android Studio, one must: Click on the "Run" tab in Android Studio and then click "Edit Configurations"
Add a new configuration.
Ensure that the Dart entry point is pointed to the main.dart file.
Save the configuration.
Run by clicking the play button found on the top tab of Android Studio (or click the Run tab and use that play button). 2.3 Building an apk file
Make sure you are at the top level of the front end directory (front_end_pocket_poll). Run the command: flutter clean
Run the command: flutter build apk --release (this builds it in release mode, if debug mode use --debug instead of --release)
The apk will be built in the build/app/outputs/apk/release folder of front_end_pocket_poll. Note if making a debug apk file the last directory in the build path will be "debug" instead of "release". 2.4 Running the application from a release .apk file
Note that attempting to install a release apk on an emulated android device will likely not work. Use a real device instead.
To run the application from a release .apk file, one must: Ensure there are no prior versions of this application installed on the android device.
Open the download location (presumably github) and download the apk directly on to the device from there. Your phone's settings might have to be altered to allow external apks to be downloaded (typically you install apks directly from Google Play, and some devices warn you when trying to download externally).
One can also download the apk file and then run this command in the downloaded directory: adb install <apk-file>. Note that you must have debugging enabled and your phone must of course be plugged into the computer. 2.5 Running the application from a debug .apk file
Note that attempting to install a debug apk on a real android device will likely not work. Use an emulator instead.
To run the application from a debug .apk file, one must: Ensure there are no prior versions of this application installed on the android device or emulator.
Drag and drop the .apk onto the device to install the application.
One can also download the apk file and then run this command in the downloaded directory: adb install <apk-file>. Note that your emulator must be turned on for this command to work.3 Deployment 3 Deployment
The backend of our application running in the AWS cloud requires deployment. This section is for the development team only as only they have access to the pocket poll AWS credentials. Please contact John Andrews () if you have any inquiries.
3.1 Deploying Lambda Functions Develop java code locally and use the command mvn package to package your java code into an executable .jar file.
Login to the AWS Management Console and navigate to the Lambda service.
Locate or create the Lambda function you want to deploy your code to.
Scroll down and upload the function, then save your changes.
If needed, change the location of the event handler to match the location in the code.
If this is the first deployment, the appropriate AWS Iam roles need to be setup so that the lambda code has authorization to access DynamoDB, Step Functions, SNS, and S3. 3.2 Deploying API Gateway Endpoints Login to the AWS Management Console and navigate to the API Gateway service.
Create a new API or make necessary changes to give API access to your lambda functions.
Click on the 'Actions' drop down and then click the deploy option.
Upon deployment, you will be able to view the link to access the API, this can be used within the dart front end code to access the backend.
If this is the first deployment, the appropriate AWS Iam roles need to be setup so that the API has authorization to access the lambda function.4 Code Style Guides: 4 Code Style Guides:5 Testing 5 Testing
5.1 Unit Testing on the Back End
5.1.1 Dependencies You must have apache installed to run the tests. 5.1.2 Running the Tests cd into the backEnd directory.
To run the tests: from the backEnd directory run this command: mvn test.
To run the tests and generate coverage reports: from the backEnd directory run this command: mvn clean verify. To view the coverage reports open the file located at backEnd/target/site/jacoco/index.html in your browser. Then use the name-links to navigate to spcific places in code. 5.1.3 Location of These Tests Our back end unit tests are located at backEnd/src/test/java. We are currently only testing our code in the imports directory, so from the above path you will have to go into the 'imports' directory to actually see the java files containing our tests. 5.2 Behavioral Testing on the Front End
5.2.1 Dependencies These tests should be run using flutter version 1.17.1 on the stable channel
To fetch project specific dependencies, run flutter pub get from the front_end_pocket_poll directory. 5.2.2 Running the Tests cd into the front_end_pocket_poll directory.
From the front_end_pocket_poll directory, to run the tests, run this command: flutter drive --target=test_driver/app.dart Note that running this test will disable the keyboard from being able to be used in subsequent launches of the app. After running tests you should uninstall the app and re-install it normally to use it.
If any tests fail it is required that the tester go in and manually delete any categories/groups that weren't deleted. The tests always delete the first item in the list, so old failed items won't be deleted unless done manually. 5.1.3 Location of These Tests Our front end behavioral tests are located at front_end_pocket_poll/test_driver/app_test.dart6 Authors 6 Authors John Andrews - Josh Rapoport - Edmond Klaric - Jeffrey Arling -
DA: 67 PA: 16 MOZ Rank: 91
