Skip to content

Itr4_Wordpress template, Plugin installation and tests

Jump to bottom
stav edited this page Jun 15, 2016 · 57 revisions

Iteration Goals

  • Building the whole wordpress website (i.e the rest of the content, other plugins the organization team require etc...)
  • Wordpress template Installation.
  • Building update DB functions.
  • Plugin final Installation.
  • Improving code.
  • Final Tests.

Roles

  • Scrum Master: guybi

Issues

  • Open issues

Iteration Result

We made code refactoring and now the code is organized and easy to edit. All the tests were passed. The plugin was installed on the server.
We optimized and improved almost every page in the plugin.
We added some DB functions for buttons we added in UI (remove selected and remove all).
We also added page for managing activities images.
The plugin is quite responsive (but not perfect). But it's not a problem because the plugin was not designed for easy mobile use (it is possible but not comfortable). We assume that the client will prefer to use the plugin with PC. If there was a significant need for mobile use, we were planning the system UI differently.

Team Cooperation

In this iteration, we worked together as much as we could (2-4 people at the time, at least one from the server's side and at least one from the client's side).
We made the integration of all the components in the system (i.e. we connected the DB to the admin page and to the website). All of this will be explained in detail as follows.

Tasks Status

  • The content will be entered by the organization. We just added some random content for visual impression.
  • We finished to install and configure the template (continued from iteration 3).
  • DB is finished. We connected all the components (buttons, tables, etc) with DB. We can save, update or remove data as we wish.
  • We installed the last version of the plugin in the server.
  • The most significant task we chose to do is code refactoring. Actually, in this iteration we optimized all what we can. We removed unnecessary code and notes, and we divided all files (CSS, JS, HTML, PHP) to seperated files for modularity.
  • We did final tests. It will be discussed in detail in Testing .

Points Summary

  • Wordpress template Installation - 8 points
  • Building update DB functions - 10 points
  • Plugin final Installation - 8 points
  • Refactoring code - 10 points
  • Final Tests - 10 points

Total: 46

Iteration Conclusion

The most important this we learned in this iteration is how to work together as a whole team.
Until now, we divided to small teams (or sometimes alone). This week, we had to do the integration of everything, therefore we had to sit together.
The work was professional, everyone knew their job and if there were problems during the integration, we fixed it very fast.
In conclusion, the decisions we made during the iterations were considered enough, with thinking about each part of the process.
For improvement we will mention that sometimes we over-estimated our time and sometimes tasks were not finished on time. Therefore, this caused unnecessary pressure.

Demonstration

  • Manage Map

  • website side

Code Review

Server Side to Client Side (public) -When pointing the cursor on the map a logo should be shown.
Server side to Client side - admin -In Manage-Activity page change the text field type from text to date.
Server side to Client side - admin -After closing the form of adding new activity you should clean the text fields values.
Client side to server side-when you change the main image you should clean the activity table in order to determine a new marker.

Testing

Most of the tests were done on the UI.
We make sure that all buttons (for add, update or remove) worked as well.
We also made validation tests in all the forms, to make sure the user will not enter invalid information.

  • Database tests:

    • Insert/Update/Delete test for map table with real values from the client side.
    • Insert/Update/Delete test for activities table with real values from the client side.
    • Insert/Update/Delete test for categories table with real values from the client side.
    • Insert/Update/Delete test for activities_image table with real values from the client side.
    • Insert unvalid values in the text filed to the dataBase in the admin side.
    • Press on the "save" button when fields are empty - required tests.
    • validation - try dropping unexist table.

  • Client side - admin

    • Validiation - we pressed on save image and upload image buttons with no values.
    • Check the connection between the DB and the client - admin.
    • Check the sort by category name in manage category page.

  • Responsive tests: Test the plugin in mobile - the test did not pass. There are issues we did not have time to solve. Read Iteration Result for more details.

Project Summary Report

Manuals:

Team's Spirit

At the beginning ,we have used the Code of Conduct for the project being at progress.
We all believed in "if it ain't broke, don't fix it". The reason we think it is relevant here is because we need to do maximum work in minimum time. We make efforts to preserve the quality of code, but one way or the other we prefer to finish the work and do code refactoring in iteration 4 as planned. Moreover, we believe in "the idea is that quality does not necessarily increase with functionality", which reinforces the idea of prefer working and less quality instead of not working and more quality.
Of course, we maintain on naming conversion, in order to make our code readable and understandable.

Developing Process

The develop progress was divided into 5 iterations:

  • Iteration 0 - ZFR - Zero Feature Release.
  • Iteration 1 - MVP - Minimum Viable Project.
  • Iteration 2 - Database and Mapify Plugin.
  • Iteration 3 - Content, UI and Mapify.
  • Iteration 4 - Wordpress template, Plugin installation and tests.

Summary for all iterations:

  • Iteration Duration - each iteration took about two weeks, it was enough time to finish all iterations' tasks (it's all about manage your time right).
  • Number of iteration - the number of the iteration was enough (maybe one is extra), it enabled us to divide the main tasks into sub-tasks per iteration. Every iteration had a context, an unique milestone, that expresses a main idea in the project.
  • Summary-points - We set the points to a scala from 8 to 13 (random numbers): 8 for easy task, 10 for medium task and 13 for hard task. In that way we can manage our tasks by the time we have to spend for them, and the complexity of the tasks - If there are things we should learn before comitting the changes.
  • Iteration conclusion - helped us to plan our next iteration better, and learn what we've done wrong in previous iterations.

Project Reflection

  • For DB management, we wanted to use mongoDB, and to established standalone database using No-SQL DB (which is easy to learn and fast DB). But while re-thinking we learned that we can use WordPress's database. The amount of data we expect to have is quite small, therefore we eventually started using WordPress's database (MySQL).
  • We had a problem that we did not know how to "connect" between PHP and Javascript and how it should work together. It took us a long time to learn how these two languages should communicate. Eventually, after a lot of effort and time we solved the problem using, among the rest, AJAX.
  • At the beginning, team's cooperation was a bit hard for some of the team. We made the work together to ensure everyone understand the plan. Afterwards, we divided to small teams (2-2-1) to split the work. We separated to client side and server side teams to ensure each team concentrate on specific part of the system. In this way, we achieved great results.

Yerusalmit Project

Clone this wiki locally