diff test/test_security.py @ 5200:16a8a3f0772c

Reset state of: self.db.security.set_props_only_default(False) at end of testGetPermission. I thought each test_X module had a fresh environment an load of all modules. I guess that is not the case as not resetting the props_only default to false seemed to bleed into the testAuthFilter in text_xmlrpc.py. However the funny part is it only caused problem in travis ci. Not in my manual running of the full test suite on two platforms. However I am pulling errors because the framework is not skipping the postgres tests for text_xmlrpc. Maybe that failure is hiding something?? If I run just the test_xmlrpc module I would not expect an issue since the security test suite won't be invoked. I am using different versions of the test harness and python so maybe.....
author John Rouillard <rouilj@ieee.org>
date Sat, 18 Mar 2017 15:12:39 -0400
parents e0732fd6a6c7
children c94fd717e28c
line wrap: on
line diff
--- a/test/test_security.py	Sat Mar 18 14:42:05 2017 -0400
+++ b/test/test_security.py	Sat Mar 18 15:12:39 2017 -0400
@@ -132,6 +132,11 @@
         self.assertEquals(get('View', 'issue', properties=['title'],
             check=dummy), apci)
 
+        # Reset to default. Somehow this setting looks like it
+        # was bleeding through to other tests in test_xmlrpc.
+        # Is the security module being loaded only once for all tests??
+        self.db.security.set_props_only_default(False)
+
     def testDBinit(self):
         self.db.user.create(username="demo", roles='User')
         self.db.user.create(username="anonymous", roles='Anonymous')

Roundup Issue Tracker: http://roundup-tracker.org/