search

t-artistik / browserscope

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

Collect sandbox data for custom tests separately #219

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
It might make sense to collect sandbox data separately from production data to 
allow mistakes during development and debugging.

Right now I had to create a separate test for debugging my code and be very 
careful not to "spoil" real test data.

Don't know how it'll work on test display - maybe add "sandbox" parameter to 
the iframe call.

Original issue reported on code.google.com by sergey.c...@gmail.com on 8 Jun 2010 at 5:00

GoogleCodeExporter commented 8 years ago 
It's probably worth adding functionality to reset sandbox data as well to clear 
the clutter of wrong variable names or broken reports.

Original comment by sergey.c...@gmail.com on 8 Jun 2010 at 5:48

GoogleCodeExporter commented 8 years ago 
While I agree this is potentially useful, I think one should just make a new 
test after debugging, or more simply, use another test_key.

Original comment by els...@gmail.com on 21 Jun 2010 at 3:58