Update the testing part of the Template

Because of the way the testing part of the specs template is written
you basically get one of 3 throw away answers in the spec.

1) we'll have unit tests
2) we'll add tempest tests
3) we'll have 3rd party testing

However, the specs *rarely* actually talk about what's actually
important to test in the feature. Which means those are all kind of
throw away statements.

A much more useful piece of information is to ask what are the
critical scenarios to test for a feature. What's really important that
works. What's really important that it doesn't break something
else. What are some interesting edge cases we should be careful about.

This is an initial stab at that paragraph change. We should probably
wordsmith on it though.

Change-Id: I83a146a4561fac50fdd3bd961d16ff32cccbf4b9

specs/kilo-template.rst

@@ -331,6 +331,11 @@ Dependencies
 Testing
 =======
 
+Please discuss the important scenarios needed to test here, as well as
+specific edge cases we should be ensuring work correctly. For each
+scenario please specify if this requires specialized hardware, a full
+openstack environment, or can be simulated inside the Nova tree.
+
 Please discuss how the change will be tested. We especially want to know what
 tempest tests will be added. It is assumed that unit test coverage will be
 added so that doesn't need to be mentioned explicitly, but discussion of why