stuartsoft / pingit Goto Github PK

Test 35 requires some way for the user to disconnect from chat, and we currently have no way to do so.

Android Butter Knife to refactor boilerplate code - if time
Dagger for testing/dependency injection
Use Scalpel for GUI debugging

Not a full issue, just putting this here so we don't forget to clean up the unnecessary comments and such.

Also in this, make spacing/line breaks consistent/clean

login w/ account A
set a notification resent
logout
login w/ account B
B has A's resend

Tapping the notification currently does nothing. It should open the app when tapped, preferably to the Pings screen.

The FAQ is functional, but it needs some polishing. Questions shouldn't awkwardly scroll inside their little window, the justification is off, and we need to test to be sure that when the categories go past the bottom of the screen everything looks good.

Probably not a big deal in real use, but JSYK

When the user opens the app for the first time, the ringtone, delay number, and name fields are incorrect. The ringtone should be the phone's default ringtone, the name should be their entered name at registration, and the delay value should be something other than null (5 minutes?)

See image for what this looks like:

https://files.slack.com/files-pri/T09LPUR3K-F0YKXR8MQ/2016-04-07_00.29.03.png

Test 49 requires us to have a toast pop up when the user clears his pings. This is just so he knows that the operation was successful.

When someone creates an account, the name they enter when registering should automatically be set to the value in the Settings under name. Right now, it's blank at first run.

We know about the memory leak, but we should do a check for this too.

The FAQ persistence does not work if you visit the Pings page from FAQ since it is two screens away (Chat is only one screen and works fine).

FAQ persists when you open Settings and press the phone's Back button to return, but it does not if you press the on-screen Up button.

When the user is in a chat, if he presses the Settings button, he is only brought back to the same Chat instance if he uses his device's Back button.

If you press the Up button, you're brought back to a new instance of Chat and lose your messages.

Not sure if we'll have time for this, but could we possibly run our app through something like this and check for accessibility red flags?

https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.auditor

https://developer.android.com/training/accessibility/testing.html

Not sure if this is worth fixing, but our current FAQ has typos, outdated information, etc. This might be worth fixing for the Sprint 3 presentation and certainly should be for the final talk, to make it look complete and professional.

I can do this, but I need to know where we can get some info. We don't have time to type this all out by hand.

This might already be the case, but I wanted to be sure we tracked it if not

This is some weird bug where the default value for the preference will not show at first run. Possible fix here:

https://stackoverflow.com/questions/7342557/listpreference-default-value-not-showing-up

When multiple admins are logged into Chat on the Web, the app only shows the first one to log in. Tapping the button connects you to that user correctly, but you are not told how many admins are online and the second (and third, etc.) admins are effectively cut off from chatting with this user.

If one admin is currently in chat with a phone user, and a second phone user opens the Chat tab, he is offered to connect with the Admin who is free. This is correct, so we only need to add a number to the app display.

We haven't been able to pinpoint this yet, but we need to fix the memory leak. We should utilize Fabric and LeakCanary here.

Fix email, so it checks length before trying to get a substring

Fixed in one minute

login with account A
start chat
logout
login with account B
B is in a chat

Not a full issue, but we need to be sure that we're happy with the FAQ and Pings page colors/fonts/etc.

These should be standardized and match between screens.