A developer's journey through BrowserCms.

Wednesday, April 3, 2013

testing's delicate balance

When adding scenarios, especially those with the @javascript tag, you may need to be aware of tables that should not be truncated, unless after truncating the tables they are seeded for the next run. This latter solution is not one we are currently using. Instead, we include the tables that are not changing, that are being used in multiple tests, in the list of exception tables that will not be truncated at the end of each scenario.

In addition to adding exception tables, you will need to include more seed data for the tables that are not being changed and are used across several scenarios.

No comments:

Post a Comment