Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Or Weekly Report #3

Open
OrAbramovich opened this issue Oct 30, 2017 · 0 comments
Open

Or Weekly Report #3

OrAbramovich opened this issue Oct 30, 2017 · 0 comments
Assignees
@OrAbramovich
Labels
Weekly Report

Comments

@OrAbramovich
Copy link
Collaborator

OrAbramovich commented Oct 30, 2017 •
edited
Loading

Semester B

25.03.2018 - 31.03.2018

  1. Integrated GitHub projects into our project.
  2. Created issues following the meeting with David.
  3. Prioritized the opened issues (with all the team).
  4. Added first meeting summary to the Wiki.
  5. Back-end: Added edit apartment route (Back-end: Add edit apartment route #193).
  6. Testing: Created tests for PATCH /apartments/id (Testing: Create tests for PATCH /apartments/id #208).
  7. Testing: Disable logger while running tests - added threshold (Testing: Disable logger while running tests #215).
  8. Back-end: Made log level configurable and environment dependent (Back-end: Make log level configurable and environment dependent #216).
  9. Back-end: Added support of default entry to the server config file (Back-end: Add support default entry to the server config file #217).
  10. Design: Document: Designed notifications feature alternatives (Document: Design notifications feature (options and general ideas) #199).

01.04.2018 - 07.04.2018 (Passover)

  1. Front-end: Added social media share buttons to ads (Front-end: Add social media share buttons to ads #219)
  2. Document: wrote the "Roommates" article with @alonttal (Document: Write an article (final report) about Roommates #197 )
  3. Raised ways to improve our matching algorithm accuracy (Discussion: Design: Hobbies and interests questionnaire #240 ).
  4. Participated in the discussion (comments) raised by team members.
  5. Back-end: wrote the visit module (Back-end: Create "Visit" module #232 ).
  6. Testing: Back-end: wrote tests for the visit module (Testing: Back-end: Create tests for "Visit" module #241 ).

08.04.2018 - 14.04.2018

  1. Searched for bugs in the project (e.g: Bug: Front-end: Add missing entrance date information to the apartment page #246, Bug: Front-end: The "WHEN" filter doesn't work #249 )
  2. Fixed bug: Front-end: Added missing entrance date information to the apartment page (Bug: Front-end: Add missing entrance date information to the apartment page #246).
  3. Fixed bug: Front-end: The "WHEN" filter doesn't work (Bug: Front-end: The "WHEN" filter doesn't work #249) .
  4. Implemented: DB: Apartment schema has to support the visits data (DB: Apartment schema has to support the visits data #231).
  5. Implemented: Back-end: notification module (Back-end: Create notification module #257 ).
  6. Testing: Back-end: created unit tests for the otification module (Testing: Back-end: Create tests for notification module  #258 ).
  7. Implemented: Back-end: Notifications aggregation policy module (Back-end: Create notifications aggregation policy module #259 ).
  8. Testing: Back-end: Created unit tests for the notifications aggregation policy module (Testing: Back-end: Create tests for notifications aggregation policy module #260 ).
  9. DB: Back-end: Changed DB schemas to support notifications feature (DB: Back-end: Change DB schemas to support notifications feature #262).
  10. Back-end: Added relevant functionalities to current models to support notifications (Back-end: Add relevant functionalities to current models to support notifications #263).
  11. Back-end: Added notifier module (Back-end: Add notifier module #264).

15.04.2018 - 21.04.2018

  1. Testing: Back-end: Added notifications related data to the seed file (infrastructure for notifications feature testing)
  2. Testing: Back-end: Created tests for the notifier module (Testing: Back-end: Create tests for the notifier module #269).
  3. Back-end: Modified current routes to push notifications (Back-end: Modify current routes to push notifications #273).
  4. Testing: Back-end: Added tests for route: PUT /apartments/:id/subscription (Testing: Back-end: Add tests for route: PUT /apartments/:id/subscription #272)
  5. Back-end: Added route: PUT /apartments/:id/subscription (Back-end: Add route: PUT /apartments/:id/subscription #270)
  6. Back-end: Added route: PATCH /users/notifications/:id (Back-end: Add route: PATCH /users/notifications/:id #279).
  7. Testing: Back-end: Added tests for route: PATCH /users/notifications/:id (Testing: Back-end: Add tests for route: PATCH /users/notifications/:id #280).
  8. Testing: Fixed notifier module tests (Testing: Fix notifier module tests #293 )
  9. Document: Wrote a document explaining the way to work with the sockets server (Document: Working with the sockets server #301 ).
  10. Back-end: Made socket server port configurable and environment dependent (Back-end: Make socket server port configurable and environment dependent #302)
  11. Back-end: Integrated the new socket server into our web application (Back-end: Integrate the new socket server into our web application #303).
  12. Back-end: Completed the implementation of a new module/server - sockets server - first phase (Back-end: Implement sockets server - first phase #294).

22.04.2018 - 28.04.2018

  1. Back-end: Implemented the second phase of the sockets server (i.e. authentication) (Back-end: Sockets server - second phase  #304).
  2. Document: Updated the "Working with the socket server" tutorial with the new parameters presented in the second phase of implementation (Document: "Working with the socket server" tutorial - second phase #307)
  3. Testing: Back-end: Added and modified tests according to the new notifications aggregation policy (Testing: Back-end: Modify the tests according to the new notifications aggregation policy #314).
  4. Back-end: Changed notifications aggregation policy (Back-end: Change notifications aggregation policy #312).
  5. Document: Updated Back-end API document with the new notifications routes (Document: Update Back-end API document with the new notifications routes #308).
  6. Document: Wrote notifications feature document (Document: Write notifications feature document #309).
  7. DB: Back-end: Added time to notification schema (DB: Back-end: Add time to notification schema #311).
  8. Back-end: Changed current functionality to support "time" property of notification (Back-end: Change current functionality to support "time" property of notification #313).
  9. Testing: Modified & added tests to validate "time" property of notification (Testing: Modify & add tests to validate "time" property of notification #318).
  10. Back-end: Integrated notifications feature with the sockets server (Back-end: Integrate notifications feature with the sockets server #295).
  11. Back-end: completed the notification system implementation (Back-end: Notification system implementation #253 ).
  12. Back-end: re-committed (and new commits of local changes) all visit feature code (Back-end: Re-commit all "schedule a visit" code #285 ): DB: Apartment schema has to support the visits data #231, Back-end: Create "Visit" module #232, Back-end: Apartment model has to support the visits functionality #233, Testing: Back-end: Create tests for "Visit" module #241 , Back-end: Create GET /apartments/visit/statuses #242 , Back-end: Create PUT /apartments/:id/visit #243 , Back-end: PATCH /apartments/:id/visit/:visitId #244 , Back-end: GET /apartments/visit/actions #250 so the "sched a visit" (Back-end: Implement "Sched a visit" feature #230 ) feature is done on back-end.
  13. Back-end: Testing: Resolved the errors in the TravisCI builds so now we can use it again (Back-end: Fix the CI builds #324 ).
  14. Bug: Back-end: Assisted Alon solving logger exception (Fix logger sometimes throwing exception #334 ).
  15. Back-end: Created route for fetching users list by ids (Back-end: Create route for fetching users list by ids #317).
  16. Testing: Back-end: Modified current & created new tests for fetching users list by ids (Testing: Back-end: Modify current & create new tests for fetching users list by ids  #337)

29.04.2018 - 05.05.2018

  1. Document: Design: Sockets server: Wrote private messaging and notifications functionalities design ( Document: Design: Sockets server: Private messaging and notifications functionalities #320).
  2. Back-end: Added functionality of "notification_read" message to the sockets server (Back-end: Add functionality of "notification_read" message to the sockets server #346).
  3. Back-end: Changed current flow & added supported messages of the sockets server according to the new design I wrote (Back-end: Change current flow & supported messages of the sockets server according to the new design #345).
  4. Back-end: Fixed Bug: Some functions in user & apartment models don't check correctly equality of objects (Back-end: Bug: Some functions in user & apartment models don't check correctly equality of objects #349).
  5. Back-end: Separated the functionality of the sockets server from the sockets server file (Back-end: Separate the functionality of the sockets server from the sockets server file #350).
  6. Back-end: Implemented: Sockets-server: Has to provide functionality and not an enum (Back-end: Sockets-server: Has to provide functionality and not an enum #357).
  7. Back-end: Added changing notification read state functionality to the notification module (Back-end: Add changing notification read state functionality to the notification module #359).
  8. Back-end: Bug: Fixed an undesired recursion caused by the merge (Back-end: Bug: Fix an undesired recursion caused by the merge #361)
  9. Testing: Back-end: Added tests for changing notification read state functionality (Testing: Back-end: Add tests for changing notification read state functionality #360).
  10. Testing: Back-end: Wrote tests for current functionalities of the sockets server (Testing: Back-end: Write tests for current functionalities of the sockets server #351).
  11. Testing: Back-end: Fixed unstable test in the notifier service (Testing: Back-end: Fix unstable test in the notifier service #365).
  12. Back-end: Wrote Design document: Support private messaging (chat) (Back-end: Design: Support private messaging (chat) #358).
  13. Back-end: DB: Created private messaging entities DB schema (Back-end: DB: Create private messaging entities DB schema #367).
  14. Back-end: Added private messaging module (Back-end: Add private messaging module #368).
  15. Testing: Back-end: Created tests for the private messaging module (Testing: Back-end: Create tests for the private messaging module #369).
  16. Document: Updated the back-end API with the new schemas (Document: Update the back-end API with the new schemas #373).

06.05.2018 - 12.05.2018

  1. Testing: Back-end: Fixed failing tests so the CI builds can pass (Testing: Back-end: Fix failing tests #376).
  2. Testing: Back-end: Fixed unstable tests (Testing: Back-end: Fix unstable tests #381).
  3. Back-end: Added notifications to the user json (Back-end: Add notifications to the user json #387).
  4. Back-end: Front-end: Notifications feature integration (back-end & front-end) with @alonttal (Back-end: Front-end: Notifications feature integration (back-end & front-end) #382).
  5. Back-end: Sockets-server: Support authentication with second roundtrip with @alonttal (Back-end: Sockets-server: Support authentication with second roundtrip #386).
  6. Front-end: Fetched self on creation with @alonttal (Fetch self on creation #388)
  7. Back-end: Fixed: build is broken (Back-end: build is broken #390).
  8. DB: Back-end: Updated user schema with the new private messaging properties (DB: Back-end: Update user schema with the new private messaging properties #370).
  9. Back-end: Updated user module with relevant functionalities for the private messaging feature (Back-end: Update user module with relevant functionalities for the private messaging feature  #374).
  10. Testing: Back-end: Created tests for the user module private messaging functionalities (Testing: Back-end: Create tests for the user module private messaging functionalities #375)

13.05.2018 - 19.05.2018

  1. Back-end: sockets server: added: handle private message request (Back-end: sockets server: handle private message request #404).
  2. Testing: Back-end: sockets server: Created tests for private message request (Testing: Back-end: sockets server: Create tests for private message request #405).
  3. Back-end: sockets server: added: handle private message read request (Back-end: sockets server: handle private message read request #409).
  4. Testing: Back-end: sockets server: Created tests for private message read request Testing: Back-end: sockets server: Create tests for private message read request #410
  5. Back-end: Implemented route delete '/users/conversation' Back-end: Implement route delete '/users/conversation' #423
  6. Testing: Back-end: Created tests for route delete '/users/conversation' Testing: Back-end: Create tests for route delete '/users/conversation' #424
  7. Back-end: Fixed Bug: User model function doesn't properly handle missing id when fetching notification Back-end: Bug: User model function doesn't properly handle missing id when fetching notification #443
  8. Back-end: Added support multiple ids on PATCH /users/notifications/:id Back-end: Support multiple ids on PATCH /users/notifications/:id #418
  9. Back-end: Updated modules following the Back-end: Support multiple ids on PATCH /users/notifications/:id #418 changes Back-end: Update modules following the #418 changes #444
  10. Testing: Back-end: Created tests for PATCH /users/notification/:id Testing: Back-end: Create tests for PATCH /users/notification/:id #426

20.05.2018 - 26.05.2018

  1. Document: Wrote Weekly Meeting Minutes 22-05-18 (Document: Write Weekly Meeting Minutes 22-05-18 #463).
  2. Back-end: Fixed: sockets server: Send private message read to front-end as object instead of string (Back-end: sockets server: Send private message read to front-end as object instead of string #472).
  3. Back-end: Fixed: sockets server: Send private message to front-end as object instead of string (Back-end: sockets server: Send private message to front-end as object instead of string #416).
  4. Wrote mid semester presentation (Document: Write mid semester POC presentation and validate it meets all requirements #449).
  5. Searched for bugs in the system (before mid semester presentation) - Back-end: Don't send notifications to front-end in case of aggregation with no new data #484, Back-end: Like apartment should add the user to the subscribers list #483, Testing: fix failing tests due to incorrect tag id #481
  6. Prepared the mid semester POC speech Must: Prepare the mid semester POC speech #456
  7. Back-end: Added private messaging functionality to the sockets server Back-end: Add private messaging functionality to the sockets server #319

27.05.2018 - 02.06.2018

  1. Searched for bugs in the system (before mid semester presentation) - Bug: Apartment floor field is optional but searching for apartment without a floor returns empty result #494 , Bug: Updating birth-date via the profile page doesnt work  #495 , Bug: Advertising apartments sliders are stuck at "0" (sometimes) #496
  2. Document: Mid semester presentation polishes Document: Mid semester presentation polish  #491
  3. Must: Prepared the mid semester POC speech - polishes Must: Prepare the mid semester POC speech #456
  4. Must: Demo dress rehearsal Must: Demo dress rehearsal #492 with Alon
  5. Must: Prepare users for the demo with Alon (Must: Prepare users for the demo #493)
  6. Front-end: Added search review component (Front-end: Provide search functionality in the reviews page #514 ).
  7. Back-end: Added route to fetch all reviews (without aggregation) (Back-end: Add route to fetch all reviews (without aggregation) #516).
  8. Fixed: Back-end: Reviews routes should return the format expected by the front-end (Back-end: Reviews routes should return the format expected by the front-end #513).
  9. Testing: Added tests to the new route which fetches all reviews (without aggregation) (Testing: Add tests to the new route which fetches all reviews (without aggregation) #517).

03.06.2018 - 09.06.2018

  1. Front-end: Provided search functionality in the reviews page (Front-end: Provide search functionality in the reviews page #514).
  2. Front-end: Integrated reviews page with back-end (Front-end: Integrate reviews page with backend #501).
  3. Front End: added the ability to add reviews in review page (Front End: add review to review page  #499).
  4. Front-end: Fixed Bug: Reviews pros and cons are not displayed in front end (Front-end: Bug: Reviews pros and cons are not displayed in front end #527).
  5. Assisted Alon with last polishes to the project poster (Create The Poster Template #519 ).
  6. Back-end: Email is case sensitive. Email is case sensitive.  #477 - fixed this bug.

10.06.2018 - 16.06.2018

  1. Email is case sensitive. Email is case sensitive.  #477 - wrote unit tests for the fix.
  2. Started working on the apartment page - two weeks job (Alon continues) - It has now the same template as the apartment details card displayed in the main page (collapsed).

Planned the architecture of the integration with Azure + implemented it:

  1. Back-end & Front-end:Azure: Deployed server to azure (Back-end & Front-end:Azure: Deploy server to azure #551) + Azure configuration
  2. DB: Azure: Deployed DB to azure (DB: Azure: Deploy DB to azure #549) + Azure configuration
  3. Back-end: DB: Azure: Configure back-end to communicate with DB on cloud Back-end: DB: Azure: Configure back-end to communicate with DB on cloud #550
  4. Started: Back-end & Front-end : Azure: Configure server to work in azure Back-end & Front-end : Azure: Configure server to work in azure #552
  5. Started: Document: DB: Azure: Write Azure DB deployment guide Document: DB: Azure: Write Azure DB deployment guide #566
  6. Started: Testing: Test integration with Azure Testing: Test integration with Azure #589 (opened bug Bug: Azure: Back-end: Verification mail is sent with "localhost" address #590 )

17.06.2018 - 25.06.2018

Continue with the Azure integration:

  1. Back-end & Front-end:Azure: Deployed server to azure (Back-end & Front-end:Azure: Deploy server to azure #551) + Azure configuration - fixed issues from past week.
  2. Continued with: Back-end & Front-end : Azure: Configure server to work in azure Back-end & Front-end : Azure: Configure server to work in azure #552
  3. Finished: Testing: Test integration with Azure Testing: Test integration with Azure #589 (opened bug Server: Azure: WebSockets don't work #595 , Bug: Front-end: Share buttons link to "localhost" instead of actual address #596 , Bug: Azure: Back-end: Reset password mail is sent with "localhost" address #598 )
  4. Fixed: Server: Azure: WebSockets don't work Server: Azure: WebSockets don't work #595

Additional items:

  1. Front-end: Removed "enable notifications" from profile component and added it to apartment page. Front-end: Remove "enable notifications" from profile component and add it to apartment page. #600
  2. Front-end: Activated option to subscribe to apartment page Front-end: Activate option to subscribe to apartment page #599
  3. The 2 above fixes the bug: Apartment page: enable notifications Apartment page: enable notifications  #593
  4. Fixed Bug: Azure: Back-end: Reset password mail is sent with "localhost" address Bug: Azure: Back-end: Reset password mail is sent with "localhost" address #598
  5. Looking for bugs for the final presentation (examples for findings Bug: Front-end: When user clicks on "accept" a group it is considered as "declined" #618 , Back-end: Front-end: Add new notification type "group accepted" #619, Bug: Front-end: Wrong error "apartment's floor number is more than the total building floors" #621, Front-end: Search doesn't work on chat page #622, Bug: Front-end: Clicking on "clear" group doesn't return group members to the available list #631 , Bug: Front-end: No reason to allow creating groups once a group was closed #632 , Bug: Front-end: Redundant caption of "ranking" appears under publisher name #633 .
  6. Fixed Bug: Front-end: When user clicks on "accept" a group it is considered as "declined" Bug: Front-end: When user clicks on "accept" a group it is considered as "declined" #618
  7. Fixed Bug: User not notified when he's in a group Bug: User not notified when he's in a group #614
  8. Back-end: Front-end: Added new notification type "group accepted" Back-end: Front-end: Add new notification type "group accepted" #619
  9. Fixed Bug: Front-end: Wrong error "apartment's floor number is more than the total building floors" Bug: Front-end: Wrong error "apartment's floor number is more than the total building floors" #621
  10. Fixed bug: owner isn't notified when a new full group is available Bug: owner isn't notified when a new full group is available #610, Notify owner on active group #508
  11. Fixed bug: Front-end: Main details date, address Bug: Front-end: Main details date, address #576
  12. Fixed bug: Weird chat behavior Bug: Weird chat behavior #617
  13. Fixed bug: Front-end: Enable notifications sent request to localhost instead of server address Bug: Front-end: Enable notifications sent request to localhost instead of server address #624
  14. Improved: Front-end: Notification should redirect to apartment page and not to search results Improvement: Front-end: Notification should redirect to apartment page and not to search results #625
  15. Fixed bug: Create Your Own Group section should not be shown if not logged in (and verified) Bug: Create Your Own Group section should not be shown if not logged in (and verified) #626
  16. Fixed bug: Both search and add review modals can be opened in reviews page Bug: Both search and add review modals can be opened in reviews page #629
  17. Fixed bug: Group style is not change after owner closes a deal. The Ad should be marked as "Deal Closed" Bug: Group style is not change after owner closes a deal. The Ad should be marked as "Deal Closed" #630
  18. Fixed bug: Front-end: Redundant caption of "ranking" appears under publisher name Bug: Front-end: Redundant caption of "ranking" appears under publisher name #633
  19. Fixed bug: Front-end: No reason to allow creating groups once a group was closed Bug: Front-end: No reason to allow creating groups once a group was closed #632
  20. Fixed bug: Front-end: Clicking on "clear" group doesn't return group members to the available list Bug: Front-end: Clicking on "clear" group doesn't return group members to the available list #631
  21. Implemented: Back-end: Azure: Send logs to accessible resource Back-end: Azure: Send logs to accessible resource #601
  22. Wrote document: Design: Back-end: Create component diagram Document: Design: Back-end: Create component diagram #634
  23. Wrote document: Design: Back-end: Create general deployment +azure deployment diagrams Document: Design: Back-end: Create general deployment +azure deployment diagrams #635
  24. Done: Testing: Improve coverage Testing: Improve coverage #620
  25. Wrote document: DB: Azure: Write Azure DB deployment guide
  26. Fixed bug: Front-end: All buttons of groups should be disabled once a group is completed Bug: Front-end: All buttons of groups should be disabled once a group is completed #642
  27. Fixed bug: Front-end: Close the deal button doesn't trigger the route that changes group status Bug: Front-end: Close the deal button doesn't trigger the route that changes group status #643
  28. Did testing: Test integration with Azure Testing: Test integration with Azure #589
  29. Implemented Back-end: Created Route for fetching Users ordered by BestMatching Create Route for fetching Users ordered by BestMatching #377
  30. Implemented Back-end: Send mail to users once group is signed Back-end: Send mail to users once group is signed #649
  31. Implemented back-end side of: Fix: Order group member suggestions ordered by matching Fix: Order group member suggestions ordered by matching #648
  32. Document: Wrote business flow Document: Write business flow #656
  33. Document: Fixed mistakes in the user's manual Continue writing user manual #603

--------

Semester A

29.10.2017 - 04.11.2017

  1. Created issues & participated in the discussion (comments) raised by them ( Design: Choose the delivered product #4 Design: Choose DB engine to be used in the project #5 Design: Choose programming language & framework to be used in the project #6 Design: Choose geo-location services provider #7 Design: Choose the main must have features #8 Project definition #12 Research: Compare DB alternatives: MongoDB & ElasticSearch  #13).
  2. Made an introduction to ElasticSearch in order to decide between MongoDB and ElasticSearch ( Introduction to Elasticsearch #18 ).
  3. Added first meeting summary to the Wiki.

05.11.2017 - 11.11.2017

  1. Created issues & participated in the discussion (comments) raised by them ( Design: Determining data to be stored & actions & data relationships #19 Design: determine DB engine must-have features #20 Research: Compare DB alternatives: MongoDB & MySQL #21 Design: DB structure #22 Design: DB design #23 ).
  2. Analyzed & defined the main data entities in the problem domain and the relationships between them ( Design: Determining data to be stored & actions & data relationships #19 ).
  3. Defined the DB must have features in order to choose the most suitable DB for our project ( Design: determine DB engine must-have features #20 )
  4. Collected the information I read and wrote a ~20 pages tutorial about: MongoDB and the integration of it with Java (with Java Driver and Spring Data) - [MongoDB tutorial] (https://github.com/TechnionYearlyProject/Roommates/files/1462328/MongoDB.Tutorial.pdf) ( Tutorial: MongoDB #28 )
  5. Planned the DB structure ( Design: DB structure #22 )

12.11.2017 - 18.11.2017

  1. Wrote HLD v1 with @alonttal ( High-Level Design Document #31 )
  2. Wrote a brief introduction to Amazon S3 ( Storage: Create a brief introduction to Amazon S3 #32 )
  3. Created a storage design ( Design: Create storage design #34 )
  4. Added weekly meeting summary to the Wiki.
  5. Checked alternative for Spring - Node.JS & Express.JS with @alonttal ( check alternative for Spring #36 )
  6. Updated HLD to v2 with @alonttal

19.11.2017 - 25.11.2017

  1. Added weekly meeting summary to the Wiki.
  2. Defined back-end-UI API functionalities ( Design: Back-end API #38 ).
  3. Studied JavaScript & Node.JS
  4. Configured DB instance to work with external back-end ( DB: Configure DB instance to work with logic server #44 ).
  5. Wrote initial draft of the DB communicator component in order to test integration of logic server and DB server ( Back-end: Configure back-end to work with DB #45 ).
  6. Created Back-end API document with @alonttal ( Design: Back-end API document #48 )

26.11.2017 - 02.12.2017

  1. Added weekly meeting summary to the Wiki.
  2. Integrated project with Travis-CI ( Testing: Integrate repository with TravisCI #50 )
  3. Added test coverage analysis tool ( Testing: Add test coverage analysis tool #51 )
  4. Wrote DB server deployment script ( DB: Create DB server deployment script #46 )
  5. Wrote DB server deployment procedure ( DB: Create deployment & system requirement doc for the DB server #47 )

03.12.2017 - 09.12.2017

  1. Added apartment geo-location query ([DB] Add geo-location query for the apartments model #55, Update geolocation query method #58 )
  2. Added apartment geo-location query tests + general testing utils (Testing: Create test for the geo-location query #56 )
  3. Added back-end connection to the DB ( Add conection to db in sever.js #57 )
  4. Configured TravisCI with a mongoDB service so we can perform DB tests on it ( Testing: Integrate repository with TravisCI #50 )
  5. Configured the server to work with Google Map API in order to get geo-location data for a query (Back-end: Get geo-location data for a given address #61 )
  6. Wrote Geo location unit tests (Testing: Write geo-location service unit tests #64 )
  7. Configured geo-location service to work with Roommates token (and not ip based) (Back-end: Configure geo-location service to work with Roommates token (and not ip based)  #70 )
  8. Started working on calculating interested matching result (Back-end: Calculate interested matching result #60 )

10.12.2017 - 16.12.2017

  1. Fixed geo-location test (Testing: Fix geo-location test  #79).
  2. Wrote array functions wrapper ( Back-end: Create a wrapper for array functions #80 ).
  3. Wrote unit tests for array functions wrapper ( Testing: Unit tests for array functions wrapper #81 ).
  4. Updated back-end API with new routes ( Back-end: Update API - add hobbies and tags GETs #73 )
  5. Created hobbies module (Back-end: Create hobbies module #71)
  6. Created matcher module (Back-end: Calculate interested matching result #60 )
  7. Modified user schema to have a reference to hobbie insted of embedded hobbie (ref to the hobbies module - Back-end: Create hobbies module #71 )
  8. Wrote functions in apartment & user schema that calculate and sort interested matching result - Back-end: Calculate interested matching result #60 .
  9. Updated the seed with data that can help us support more complex tests.
  10. Wrote unit tests for Hobbie module (Testing: Unit tests for hobbies module #75 ).
  11. Wrote unit tests for Matcher module (part of Testing: Unit tests for interested matching #76 )
  12. Wrote user & apartment modules unit tests for interested matching ( Testing: Unit tests for interested matching #76 )

17.12.2017 - 23.12.2017 (Hanukkah)

  1. Fixed CI integration - builds are not triggered by push (Testing: Fix CI integration #88)
  2. Fixed CI to run all tests (Testing: CI doesn't run all tests #91 )
  3. Integrated CI with codecov - CI sends the report to codecov.io automatically (on each successful build). (Testing: Add code coverage tracker #92 ).
  4. Wrote apartment tags module (Back-end: Create tags module #72 ).
  5. Updated apartment schema to work with the tags module (Back-end: Create tags module #72)
  6. Wrote unit tests & added route tests for the tag module (Testing: Create tests for tag module #107 )
  7. Wrote POC presentation (general & backend content) with @alonttal (POC: Write POC presentation #111 , Sprint One - presentation #113 )

24.12.2017 - 30.12.2017

  1. Updated POC presentation (general & backend content) with @alonttal (POC: Write POC presentation #111 , Sprint One - presentation #113 )
  2. Found template which is going to be the goal of the UI (Front-end: Check integration of web template with Vue #112 )
  3. Wrote "add comment" route (Back-end: Implement "Add comment" route #96 )
  4. Wrote "add comment" route tests (Testing: add tests to the "add comment" route #115 )
  5. Wrote "remove apartment" route (Back-end: Implement "Remove apartment" route #97 )
  6. Wrote "remove apartment" route tests (Testing: add tests to the "remove apartment" route #117 )
  7. Started learning HTML & CSS in order to help UI tasks.
  8. Wrote "return all user tags" route (Back-end: Implement "return all user tags" route #120 ).
  9. Added new functionality to helpers.
  10. Mapped the status of all routes (Back-end: Complete all back-end routes (+tests) #125 )

31.12.2017 - 06.01.2018

  1. Wrote "return all apartment tags" route (Back-end: Implement "return all apartment tags" route #121 ).
  2. Wrote "return all user tags" route tests (Testing: Add tests to the "return all user tags" route #122 ).
  3. Wrote "return all apartment tags" route tests (Testing: Add tests to the "return all apartment tags" route #123 ).
  4. Wrote generic card component for the Front End (Front-end: Create generic card component #128 ).
  5. Wrote generic multiple select list component for the Front End (Front-end: Create generic multiple select list component #129 )
  6. Wrote user control panel page - Front End(Front-end: Create user control panel #133)
  7. Wrote user profile page (including sub componenets) - Front End (Front-end: Create user profile page #135 ).
  8. Wrote tags selection page - Front End (Front-end: Create hobbies selection page #136 ).
  9. Refactoring of some Front End components.

07.01.2018 - 13.01.2018

  1. Changed user profile page components to support dynamic data fetch from server (part of Front-end: Create user profile page #135).
  2. Changed user profile page to support dynamic data fetch from server (part of Front-end: Create user profile page #135).
  3. Bug fixes in user profile page (part of Front-end: Create user profile page #135 ).
  4. Bug fixes in user profile page components (part of Front-end: Create user profile page #135 ).
  5. Hobbies selection page to fetch data dynamically from server (part of Front-end: Create hobbies selection page #136 ).
  6. Modified user panel to fetch data dynamically from server and to send it to pages accessible from it (part of Front-end: Create user control panel #133).
  7. Added routes to new pages.
  8. Bug fixes in profile tags (part of Front-end: Create user profile page #135 )
  9. Fixed minor UI issues in the profile page (following our conversation) (Front-end: Fix minor UI issues in the profile page (following our conversation) #144 )
  10. Fixed minor UI issues in the control panel page (following our conversation) (Front-end: Fix minor UI issues in the control panel page (following our conversation) #143 )
  11. Added error logs (to the console) in user profile page and hobbies selection page.
  12. Make the buttons (submit & cancel) work against server in the hobbies selection page.
  13. Back-end - added "toggling interested state" route (including apartment & users member functions) (Back-end: Implement "toggle interested state" route #119 ).
  14. Added tests to the "toggle interested state" route (Testing: Add tests to the "toggle interested state" route #124)
  15. Linked new pages to the user control panel page (part of Front-end: Create user control panel #133).
  16. Started creating "my apartments" page (Front-end: Create my apartments page #149 ).

14.01.2018 - 22.01.2018

  1. Front-end: integrated control panel with the login mechanism (Front-end: Integrate control panel with login mechanism #155)
  2. Front-end: added status message to the hobbies selection page (Front-end: Add status message to the hobbies selection page #156)
  3. Finished hobbies selection page (Front-end: Create hobbies selection page #136 ).
  4. Front-end: Fixed bug : display readable birth-date in the profile page (not unix timestamp) (Front-end: display readable birth-date in the profile page (not unix timestamp) #157 ).
  5. Front-end: Fixed missing "profile" icon in control panel (Front-end: Fix missing "profile" icon in control panel #158).
  6. Front-end: (initial) wrote my apartments page + dynamic data fetch (Front-end: Create my apartments page #149 ).
  7. Added weekly meeting summary to the Wiki.
  8. Front-end: integrated my apartments page to the control panel (part of Front-end: Create my apartments page #149).
  9. Back-end: Created a logger module (Back-end: Create logger #59 ).
  10. Back-end: Created default exception handler (Back-end: Add default exception handler #165 )
  11. Wrote developer guide (Document: Write developer manual #162 ).
  12. Back-end: Added HTTP requests auto logger (Back-end: Add HTTP requests auto logger #166)
  13. Converted console prints to logger prints (part of Back-end: Create logger #59 ).
  14. Back-end: Fixed bug: Server crash (Bug: Server crash #173).
  15. Back-end: fixed bug: not all HTTP errors are recorded (Back-end: Bug: not all HTTP errors are recorded #174)
  16. Front-end: Fixed: published apartments list should be updated on delete - status message was added (Front-end: Published apartments list should be updated on delete #175)
  17. Front-end: Fixed all errors in control panel page (Front-end: Fix all errors in control panel page #176).
  18. Front-end: Fixed all errors in user profile page (Front-end: Fix all errors in user profile page #177).
  19. Back-end: Improved & enriched HTTP requests logger (Back-end: Improve & enrich HTTP requests logger #178).
  20. Front-end: Fixed bug: Enable user to express interest (Front-end: Bug: Enable user to express interest #181).
  21. Worked on the final presentation (Create Final Presentation #161 ).
  22. Wrote route of get interested by match (Back-end: Add route - get interested by match #182 ).
  23. Wrote unit tests for route - get interested by match (Back-end: Testing: test route - get interested by match #183 )
  24. Fixed back-end: bug: Filter by tags doesn't require all tags to match (Back-end: Bug: Filter by tags doesn't require all tags to match #184)
  25. Added data to the demo
  26. Added some documentation to back-end Add some documentation to back-end #179
  27. Fixed front-end: Bug: Apartment page carousel doesn't work Front-end: Bug: Apartment page carousel doesn't work #186
  28. Fixed Front-end: Bug: Apartment header isn't refreshed on search (main page) Front-end: Bug: Apartment header isn't refreshed on search (main page) #187.
  29. Fixed Front-end: Bug: Tags are incorrect in apartment page Front-end: Bug: Tags are incorrect in apartment page #188
  30. Fixed: Front end: Bug: interested page isn't drawn Front end: Bug: interested page isn't drawn #189.
  31. Testing: performed manual tests on the website.
  32. Presentation: preparations for the end of semster presentation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@OrAbramovich OrAbramovich

Labels
Weekly Report
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@OrAbramovich