The notify system test was using a dynamic zone for reload testing

so it was just a plain fluke that it ever succeeded.
* use a normal (non-dynamic) zone.
* check that reloads of the master zone actually occur.
* remove example3 test from tests.sh as it wasn't testing notify.
* add a "sleep 1" so that the copied file will have a newer timestamp.
* improve system test logging.
* using seperate output files for each test so that it is possible
  to work out what went wrong if the system test fails.
This commit is contained in:
Mark Andrews
2011-10-17 01:33:28 +00:00
parent 02265237cd
commit 2da036f231
3 changed files with 70 additions and 46 deletions

View File

@@ -15,12 +15,12 @@
# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
# PERFORMANCE OF THIS SOFTWARE.
# $Id: clean.sh,v 1.12 2007/09/26 03:22:44 marka Exp $
# $Id: clean.sh,v 1.13 2011/10/17 01:33:27 marka Exp $
#
# Clean up after zone transfer tests.
#
rm -f ns3/example.bk dig.out.ns2 dig.out.ns3
rm -f ns3/example.bk dig.out.ns2.test* dig.out.ns3.test*
rm -f ns2/example.db
rm -f */named.memstats