mooseman456 / lightwait Goto Github PK

It works on the other pages, but doesn't work on the queue page.

Recommendation: Use the entire div element for queue item as a button for bump due to order ingredients variation moving the bump button.

How to reproduce bug:
-Open app and tap on Grab 'N Go
-Tap top left to go back to home screen
-Grab 'N Go text is now blue
-Same with Custom Order
-But, if you go in and out of Saved Orders, text colors will reset back to gray

If I log in as chef and change something to out-of-stock, then log in as customer, the item doesn't show up on the menu at all. The release doc says it should be greyed out and unselectable.

On the admin users page, I can enter bogus info for email with correct info everywhere else and login successfully for both creating a chef and creating a admin. As well as on the user registration, I can enter bogus info on email and correct info everywhere else and successfully register and login.

After ordering, if "Return Home" is clicked then the user is taken back to the login page and seems to be logged out. Another order cannot be placed without logging back in.

If a user wants to, allows them to save an order that they can order later on

1. Save the order name to the orderNames.out file
2. Save the NSMutableDictionary from when the user created the order to the iPhone's NSDocumentDirectory.

Major login and logout network get/post calls are "pending" and ultimately fail.

After bumping all orders, if one presses recall multiple times it cause unpredictable behavior (sometimes recalls one order, sometimes more).

I registered with 'bogus' as the email with correct info everywhere else 3 times. The first time I used the password "11111111", the second time I used the same password, the third time I used "11112222". Then when logging in with the third credentials, I broke the user page:

At first it would return bumped orders back to the queue, then it caused the page to become unresponsive, then it started doing nothing upon reload.

Have the ability to scroll through multiple pages of orders.

1. Implement a next page button (grey when on last page)
2. Implement a previous page button (grey when on first page)
3. Implement a first page button (grey when on first page)

Allow the mobile user to be able to view the food stuff sold at Mac's place outside of the grill. The data will be downloaded from the database, inserted into an NSDictionary, and then loaded into a table view.

I saw this as I was testing

In the Iteration release document, you mention that neither login nor registration works. From the looks of the website on both the production server and on a localhost, nothing seems to be functional - nothing that is intrinsically 'testable' at least. The release documunt doesn't specify what we're testing either, and links to the iteration 1 document where a lot of the testable features don't seem to implemented.

Could you add what you want us to test onto the release document?

Hitting back on user account after logging in and out of admin account can get me to Administrator home where I can access all admin functions

When going to the submit order screen on the production server and hitting the submit button, the form redirects to a localhost link. Locally, there is nothing on the order screen.

Create underlying structure for the chef page.

1. Write HTML for page
2. Write CSS for page

When we were inviting users and setting a group to a UPresent, occasionally members of the group could not see the UPresent they were invited too.

Currently, the application will accept valid input then “successfully login”, however, the validation is done correctly in the php/mysql code…

THE ERROR location:
function logIn(email, password) in account.js

Successful Log In occurs when no errors occur... this is wrong because false input can be put in and throw no errors. The code needs to look at the JSON returned from Slim (the function logIn($email, $password)) in Web/api/index.php to determine if the credentials match to the database.

Alec Siems

Create underlying structure for the chef page.

1. Write HTML for page
2. Write CSS for page

Currently, any account made will simply be added to the users table, whether it be customer, chef, or administration. The database has no way of knowing the difference between any of these accounts, and thus it is also not accounted for in our code.

When you have more than eight orders, if the user is on the first page, he should not be able to see a left arrow. Same if he is on the last page, he shouldn't see a right arrow.

I tried to enter a Test item in each category with the format : "Test Category Item" and they all came out as "test category item."

Login is not functional

The phone number field on the front page will take any character

Allow the user to select the ingredients they want in their order.

1. Add selected ingredients to an NSMutableDictionary

When I enter an invalid email and/or phone number on the registration form, it does nothing. No alerts or refreshing. I found it doesn't add it to your db either because I could not log-in with the invalid info.

Displays and loads a saved order.

1. Load the orderNames.out file containing the names of all orders
2. Load the order that was clicked on

When bumping more than three orders in a row, recall will recall one order and then it will recall two orders and then even more the next time.

When bumping three orders, the third is recalled correctly but the first and second are both recalled when clicking recall the second time.

The app is loading only a default list of items that is hardcoded in GrabViewController.m file, instead of loading it from a JSON provided from the server, as the iteration document defined.

This will allow the user to see the ingredients when making a custom order.

1. Download the most recent custom menu from the database
2. Parse the JSON file into an NSDictionary
3. Load the data into different tables

Saves the order inside of the database to be viewed by the administrata later.

1. Convert selected items from the NSMutableDictionary into JSON format
2. Upload parsed file to the database

If I login on Chef, logout, then login on User and press back, I can get to the Chef's view of the queue and I can bump and recall orders. Also, recall started working again here.

If no bases are available for ordering, the user should not be able to order or just get a side. Right now the base category of the order page is just empty if no bases are available.

Idea: Add user comments to order page for adding dietary restrictions or special requests for the preparation of their meal.

After finding all the previous issues, I logged in with a legitimate account and created three new orders. Then I went to the chef's account and the queue was empty.

I entered correct email, password, and phone with *'s for first and last names and there were no alerts and the page went nowhere.
Also I tried entering bogus info for email and pass and it seemed to work, but when I tried to log in, it gave me the "password not valid" and "password and email don't match."

Will recall the most recently bumped order that is not already in the queue.

1. Implement an actual recall button
2. Replace order in the order queue window, reposition the other orders in the queue
3. Update the database to reflect that the order is active again

Entering something that is not an email in the email box or phone number in the phone number box when creating an account is accepted.
The email input is not checked to ensure that a valid email was given.
The phone number input is not checked to ensure that it is only number.

The database information for the mobile and web client will be obtained through the RESTful API middleware.

1. Create .htaccess file
2. Define the routes
3. Test the routes by verifying if they contain the proper operations

Removes an order from any position in the queue. Includes visually removing the order from the chef order queue.

1. Implement an actual bump button
2. Remove the order from the order queue
3. Update the database to reflect that the order is completed
4. Update the database to include when the order was completed

Seems to not depend on what exactly is submitted. I tried about 5 different combinations of toppings / cheese / fries and kept getting this error.

While navigating the website, the links on the top right corner of the website change in an inconsistent and unpredictable manner. This generates confusion and difficulty for the user. I suggest that maybe all links (queue, account, order, etc) should be static throughout the website to make it easier to navigate and more consistent.

As a user, I can't edit my account info, even if its all valid. It seems like it works, but if I log out I can't log in with the new information, the old still works though.

Your Release doc says that Users should be able to verify orders showing up in the queue but I don't even seem to have access to the queue as a user.

Shows the orders that have been input by mobile users

1. Parse order JSON
2. Update table with new orders