Itr3_Content, UI and Mapify - talshi/Yerushalmit GitHub Wiki

Iteration Goals

• Entering content.
• Main UI characterization and style.
• Complete unfinished goals from the previous iteration.
• Fix bugs and problems.

Roles

• Scrum Master: gabrielaes

Issues

• Open issues

• Closed issues

Iteration Result

The plugin is almost finished.
There is DB ready to use and the UI is finished (except for some not significant fixes we may do).
We are working now and in the next iteration on the website and how to inject the plugin in it.
That's the 'simple' task which left.
More information about specific details are explained as follows.

Team Cooperation

We continue to work as separated teams - server's side and client's side. We also work using git branches, each of us worked on his branch.

Tasks Status

• We installed the template ahead of schedule and we started to insert some content.
• We finished the plugin's core (the minimum features to have according to requirements).
• We made tests especially on DB, but also on UI, as detailed as follows.
• We finished undone tasks from previous iteration.

Points Summary

• Upload image 10 points
• System tests 8 points
• UI design fixes 10 points
• Build DB functions 10 points
• Site construction and design 13 points
• Building the manage category page 10 points

Total:61 points

Iteration Conclusion

We did all what we expected as mention in tasks status.
We learn how to work with WordPress DB.
We learn how to make significant validations for forms (client and server validations).
In this iteration we used AngularJS in client's side, git branches for organized work, git tags. We are also going to do code refactoring in the next iteration (all was learned in the lectures).

Demonstration

Code Review

• Server Side to Client Side - Matching table values of admin side activities and DB activities table.

• Client Side to Server Side - Pay attention when you deactivate the plugin and the table does not exist (edge case).

Testing

Testing was NOT made by TDD method.
We decided it is too late to use TDD in this stage, because the plugin almost finished.
(note: we checked for unit test library for PHP called PHPUnit. This is HUGE library that we have no time to learn in our schedule, and as mention, we need to write the tests before things get done - so it is not relevant).

However, we did some other tests as following.

• Database tests.
  • Insert/Update/Delete test for map table.
  • Insert/Update/Delete test for activities table.
  • Insert/Update/Delete test for categories table.
  • Add/Delete buttons test.
• UI functionality tests.
  • Create mock object for demonstrate add or remove map, activity or category from table (table will be shown in site).
  • UI visual test (there is no way to test the design, only simple tests for the general functionallity)
  • Responsive UI - we checked that the plugin supports Chrome, Firefox, Opera, IE, and also that it is responsive (mobile support).

Next Iteration

In the next iteration, we will concentrate in the visual site (not the site admin interface). We will inject the plugin to site and check everything is working as fine.
Iteration 4