CS373-IDB

Team Pokemon presentation

Transcript

1. Group 4: Team Pokemon Cedric Charly, Paola Jara, Ali Rashed, Will Truong, Samuel Williamson
2. What we modeled • Topic: Pokemon • Pillars: Pokedexes, Pokemon, Moves
3. Demonstration Pokemans
4. Statistics (Issues) • Github Issue Tracker ◦ Breakdown by member: ▪ Cedric: ▪ Ali: ▪ Will: ▪ Samuel: ▪ Paola: ◦ Issues Resolved: 59 ◦ Issues Unresolved: 1 • Types of Issues (labels) ◦ frontend, api, data management, documentation, testing, final presentation
5. Statistics (Unit Tests) • Used Pytest • Unit Tests: ◦ Breakdown by member: ▪ Cedric: 21 ▪ Ali: 10 ▪ Will: 9 ▪ Samuel: 10 ▪ Paola: 10 ◦ Total Unit Tests: 60
6. Critique: Our website • What did we do well? ◦ API and models are well tested → confidence in backend ◦ Separation of test database and production database ◦ Clean design, website is easy to use • What did we learn? ◦ Benefits of branching for features and reviewing PR’s before merging ▪ feature_branch → staging → master ◦ Mocking API responses to work on the frontend concurrently with backend ◦ Splitting a large feature (e.g. search) into smaller tasks
7. Critique: Our website • What can we do better? ◦ Automated tests for frontend ◦ Refactor frontend ▪ Extract common functionality in controllers ◦ Improve data models ▪ Add statistics for a Pokemon (HP, Attack, Defense, etc.) ▪ Add other pillars and relationships: Regions, Games, Abilities, Type, Evolutions • What puzzles us? ◦ Improving search (moving past full-text search and returning most relevant results) ◦ Sorting the entire data set when the data is paginated on the server-side
8. Critique: Team Books • What did they do well? ◦ Useful database - interesting and relevant fields in their models • What did we learn from their website? ◦ We liked their pagination: adjusting the number of entries per page ◦ Filtering by text is nice ◦ The loading graphic on their model pages is a good visual. • What can they do better? ◦ Adjust the design of the instance pages - there’s a lot of empty space on some pages • What puzzles us about their website? ◦ The Authors table has scrolling built into it, making it a little confusing to navigate ▪ Two layers of scrolling: one on the webpage, one on the table
9. Let’s run the unit tests!