From e0875960945a5ac2c8377c9c381c4125a8ad8f0c Mon Sep 17 00:00:00 2001 From: Travis Dart Date: Thu, 23 Jul 2020 22:59:06 -0500 Subject: [PATCH] Bugfix for travis-ci, per https://travis-ci.community/t/unexpected-build-failure-segmentation-fault/2127 --- .travis.yml | 1 + README.md | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/.travis.yml b/.travis.yml index 923e211..b8ded0c 100644 --- a/.travis.yml +++ b/.travis.yml @@ -1,4 +1,5 @@ language: python +dist: bionic python: - 2.7 - 3.8 diff --git a/README.md b/README.md index ff47500..d675378 100644 --- a/README.md +++ b/README.md @@ -100,7 +100,6 @@ Validating multi-field constraints can be tested by specifying the values (as a - End-to-end testing (with Selenium): This is partially implemented, and most of the necessary FormStorm functions have been abstracted. Just need to subclass FormTest and fully implement. - Tests for DRF Serializers. "SerializerStorm" -- Set up CI - Handle the obscure, "long tail" cases by implementing a framework to define tests for any type of constraint (such as multi-column uniqueness constraints). To do this, a "sub-test" would define one or more form submissions and the (boolean) result expected. Sub-tests would be combined with each other and with the standard combinatorial mix of good/bad values so that all fields are tested simultaneously.