Mazz Mosley 67995ab9e3 Pre-process validation steps ... In order to validate a service name that has been specified as an integer we need to run that as a pre-process validation step *before* we pass the config to be validated against the schema. It is not possible to validate it *in* the schema, it causes a type error. Even though a number is a valid service name, it must be a cast as a string within the yaml to avoid type error. Taken this opportunity to move the code design in a direction towards: 1. pre-process 2. validate 3. construct Signed-off-by: Mazz Mosley <mazz@houseofmnowster.com>		2015-08-13 16:32:20 +01:00
..
cli	[pep8] make test files and config files pep8 valid	2015-03-25 20:20:38 -07:00
__init__.py	Split tests into unit and integration	2014-04-25 22:58:21 +01:00
cli_test.py	Remove logging test	2015-07-21 15:56:37 +01:00
config_test.py	Pre-process validation steps	2015-08-13 16:32:20 +01:00
container_test.py	Use 'top' instead of 'sleep' as a dummy command	2015-05-21 16:24:29 +01:00
interpolation_test.py	Avoid duplicate warnings if an unset env variable is used multiple times	2015-08-12 15:39:33 +01:00
log_printer_test.py	WIP: rename Fig to Compose	2015-01-20 21:00:23 +00:00
multiplexer_test.py	Make sure an exception in any iterator gets raised in the main thread	2015-07-29 19:42:33 +01:00
progress_stream_test.py	Possible division by zero error when pulling an image - fixes #1463	2015-05-26 15:34:34 -07:00
project_test.py	Ignore containers that don't have a name	2015-08-10 16:29:12 +01:00
service_test.py	Merge pull request #1827 from mnowster/port-ranges	2015-08-12 11:17:22 +01:00
sort_service_test.py	Make volumes_from and net containers first class dependencies and	2015-03-06 13:30:56 -08:00
split_buffer_test.py	[pep8] make test files and config files pep8 valid	2015-03-25 20:20:38 -07:00