-
Notifications
You must be signed in to change notification settings - Fork 0
Will's Personal Log
Updated presentation slides and website. discussed a plan for presenting.
Continuing to work with Steven on Unit Testing despite my primary computer source being dead. We've met with a professional to discuss strategies. I have and plan to reach out to the team to assure everything is in order for demo day
Met with the clients again and discussed more in depth how the app would likely be used. We're hoping to add some last features (email snack log) before our final release. Recorded and edited our demonstration video. My laptop died and I am in search for a replacement or temporary computer to use for further contributions.
Having issues testing "FitLivin" as my device isn't supported. I've been trying multiple emulators and documenting what I can find using that method. Also participated in an actual diet assessment.
Enhanced Client List to show latest entry time. Enhanced PreviousEntries with a scroll listener to only load a limited number of entries at a time. Tested other members code and noted bugs. Met with the clients to show our progress and scheduled an actual diet assessment with them to better our understanding of the requirements of SnackTrack.
Reviewed, assessed, and fixed multiple issues documented by Vidal's beta release testing. Currently working on noted enhancements.
Spring Break. Explained solutions to other members who were having problems with code I had written.
Fixed color & alignment issues in SnackDetails and PreviousEntries. Other minor fixes and polishing for beta release.
Full editing capabilities are in place for a snack entry. One can touch a pencil icon to edit their entry when viewing the details (which turns the controls into edit mode) and can then be saved by pushing the save disk icon (returning the controls to a read-only mode). It took a few days for me to debug as returning to the previous entries fragment still showed the edit icon. I thought surely this was an issue with the menu/action bar and looked up all sorts of tips/tricks to clear the menu and reform it, however upon closer inspection I realized I had in fact loaded the details fragment over the top of the previous fragment instead of replacing it. This lead to the menu indeed being cleared but recreated by the details fragment as well as the previous fragment as the details fragment had not been destroyed/removed.
I've successfully been able to update the photo of a parse entry within the SnackDetailsFragment. This a big breakthrough as updating the meal type and description should follow a similar routine. Besides the act of updating, I intend to reconstruct part of the UI to enter into and out of an edit mode.
I've written a few instrumentation/behavioral tests for our app. Unit testing at this time is a bit difficult to implement due to the structure of our code (there just aren't many functions able to run unit tests on smoothly). I've successfully been able to simulate all sorts of user interaction with the app. I've made use of a tool "Robotium" to aid in this testing process. Robotium allows one to record all of their interactions with an app and convert that recording into concise and detailed testing code. Aside from the recording feature, the tool itself can be used to write testing code more simply.
This week I began researching different testing strategies to use for our app. In addition to reading the documentation, I have watched a few video tutorials on the process.
Nothing.
Worked on presentation slides and tested presentation equipment.
pushed changes to my branch and merged with master. Worked with john to resolve conflicts and integrate our work. app has basic functionality.
I've got a working listview that pulls data from parse and displays a photo overlayed with its entry date in a scrollable format. Photos respond well to different screen orientations.
I've begun work on the ListView implementation where users may scroll through their past entries. https://parse.com/docs/android/guide ParseQueryAdapter seems to be deprecated so I will be using ArrayAdapter. I've created some test data in our parse data browser to work with.
I've created a parse.com account; I believe are team is taking this route for our back-end storage. I also made my first commits/requests to and from github and android studio.
This Week I constructed a UML design for our app with input from the team. I believe I've solved most of my gradle build issues (time went from ~10 minutes to ~20 seconds).
This week Columbia was devastated by flooding and rain-waters. I didn't spend very much time on the diet app.
I ordered an android device off amazon.com and set it up to work with android studio. I have successfully been able test my code on the device. Also, our group got together to produce a detailed layout of our application. Currently practicing with ListView and DrawerLayout controls.
This week I continued to work with android studio but made little progress as the emulator (still, after re-installation with modified settings) worked very poorly; I've begun searching for an android device to use for testing. I also attended Mr. Vidal's biweekly meeting.
I brainstormed ideas for a user interface and drew a few screens to display my ideas. I also came up with 2 Personas that represent unique users of our app. I also attended a workshop by 52inc for android app development in effort to better understand the foundations of development.
Met with instructor as well as clients to discuss the bigger picture of the project. I've downloaded android studio and begun debugging my first "hello world" app. I've also started to think about ways to handle access of submitted photos.
This week I proposed a group time to accomplish Milestone 1. At this meaning I engaged in the group discussion regarding meeting times, approaches, and strategies. I've begun to research Android app development tools.