DEV - Create Test Drive app (MOBILITY-620)

[MOBILITY-622] DEV - update the bundled dining hall data to reflect real word menu choices Created: 05/May/14  Updated: 20/May/14  Resolved: 16/May/14

Status: Resolved
Project: Kuali Mobility
Component/s: Dining, Marketing
Affects Version/s: 3.1
Fix Version/s: 3.2

Type: Sub Task Priority: Major
Reporter: Joe Swanson (Inactive) Assignee: NurulHaque Murshed
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0 minutes
Time Spent: 2 days
Original Estimate: 4 hours

Rank (Obsolete): 109986
Global Rank: 86422
Sprint: Mobility 3.2, Mobility 3.3

 Description   

Update the sample data for the dining app included in the dining-config project at src/main/resources/ in DiningHalls*.xml files. The data should represent common food items and categories rather than the filler text that exists now. Additionally the dining halls should be renamed to something more in line with a restaurant name.

The DiningHallsC.xml file contains a meal that is not being served (breakfast). This should be preserved to demonstrate the varied UI behavior in this case.

One dining hall other than C should have its address removed so that the UI response to that scenario can be demonstrated.

Not all menu items need to have descriptions. In fact, at most half should have them to add variance to the display.

Do not remove pricing, serving size or calorie data from the menu items. You may change the menu item attributes (vegan, vegetarian, gluten free, halal, etc) to match the menu item if you like, but that is not necessary so long as there are some attributes left in the menus.

The menus may be shortened or varied in length so long as there are at least 15 items and 2 categories minimum per menu, excepting the Dining Hall C meal that is not being served.



 Comments   
Comment by NurulHaque Murshed [ 20/May/14 ]

As per the JIRA description, any one dining hall other than C should have its address removed. I just removed the address tag for DiningHall B (DiningHallB.xml).

Generated at Sat Apr 04 03:05:43 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.