From f8fdb500cc705e2b8b4a74166ceb2c6d8cee3fd3 Mon Sep 17 00:00:00 2001
From: Karen Arutyunov <karen@codesynthesis.com>
Date: Tue, 4 Sep 2018 14:02:11 +0300
Subject: Rename .test/test{} to .testscript/testscript{}

---
 tests/config.test | 27 ---------------------------
 1 file changed, 27 deletions(-)
 delete mode 100644 tests/config.test

(limited to 'tests/config.test')

diff --git a/tests/config.test b/tests/config.test
deleted file mode 100644
index cd5eb12..0000000
--- a/tests/config.test
+++ /dev/null
@@ -1,27 +0,0 @@
-# file      : tests/config.test
-# copyright : Copyright (c) 2014-2018 Code Synthesis Ltd
-# license   : MIT; see accompanying LICENSE file
-
-# Create an empty configuration that will be copied by subsequent tests and
-# scopes setup commands. The common approach will be that group scopes copy and
-# modify the parent scope configuration as required by the nested tests and
-# scopes. Tests will also clone the parent scope configuration to optionally
-# modify it, use and cleanup at the end. Note that configuration can not be
-# shared between multiple bpkg processes. Also we need to make sure that
-# configurations are not cloned while being used by bpkg.
-#
-+$cfg_create -d cfg 2>- &cfg/***
-
-# The most commonly used configuration cloning command that copies it from the
-# parent scope working directory.
-#
-clone_cfg = cp -p -r ../cfg ./
-
-# Clones the original (presumably empty) configuration from the root scope
-# working directory.
-#
-clone_root_cfg = cp -p -r $~/cfg ./
-
-# Setup a test command to use a cloned configuration directory by default.
-#
-test.arguments += -d cfg
-- 
cgit v1.1