search

dumre0707 / googlepersonfinder

Automatically exported from code.google.com/p/googlepersonfinder
Apache License 2.0
0 stars 0 forks source link

Implement "test mode" #99

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Implement "test mode", in which an instance may be used for drills and 
integration test with partners.

Features to implement:
  (1) on every page (including admin page), the header states that the instance is in test mode.
  (2) add an option in the admin page to switch between production mode and test mode. test entries may need to be deleted when switched to production mode.
  (3) expiration of every new entry can only be set to "2 hours" (or longer?) to prevent spammy entries from accumulating.
  (4) delete_person cron task may need to run more frequently to enable this short expiration.

Original issue reported on code.google.com by r...@google.com on 29 Mar 2012 at 3:27

GoogleCodeExporter commented 9 years ago 
Ka-Ping, does Ryo's feature list sound good to you? If so, I'll start 
implementation.

Original comment by ichik...@google.com on 29 Mar 2012 at 4:29

GoogleCodeExporter commented 9 years ago 
The feature list sounds good, but I feel I need more clarity on the decision of 
whether to have separate test-mode / real-mode instances, or to allow an 
instance to switch between test-mode and real-mode.  Could you or Ryo write up 
a requirements document for test mode, and in it specifically address possible 
solutions for separating test-mode data from real-mode data?  I'd like us to 
walk through exactly what happens when we need to do a real launch, and 
evaluate the benefits and risks of each option, where the options might include:
(a) Just use separate test-mode and real-mode repositories
(b) Use a single repository but when the switch is flipped, the data is cleaned 
up (Does the repo go into read-only state during deletion? What if users start 
entering real records before the switch is flipped? etc.)
(c) Use a single repository but modify the key_name prefix somehow to separate 
the data
(d) Other possibilities...?

Original comment by kpy@google.com on 30 Mar 2012 at 7:47

GoogleCodeExporter commented 9 years ago 
Sure I will in the next week, probably with Nobu-san who suggested the original 
idea.

Original comment by ichik...@google.com on 30 Mar 2012 at 7:56

GoogleCodeExporter commented 9 years ago

Original comment by r...@google.com on 5 Jul 2012 at 1:46