Added parSafe=false to a test
Merge pull request #602 from vasslitvinov/add_parSafe=false_in_a_test

Added parSafe=false to a test

This test already locks on domain modifications, so it should work with parSafe=false.
So I am making this one more test to exercise not-parSafe-ness.

Reviewed by Ben.