...
NUnit Property Attribute: If a case has been created in AIO Tests, The Property attribute can be used with AIO property name :
aioCaseKey
Code Block [Test] [Property("aiocasekey", "RAM-TC-1")] [Category("SimpleTests")] public void PassingTest() { Assert.Pass(); }
Testcase key in Underscores in test name : Since many languages do not allow hyphens in their method signatures, AIO Tests allows case keys with underscores as valid mapping. The AIO Test key can be used in the method name by replacing the hyphen with underscores. eg. if AT-TC-123 is being automated by a test, the test method can be named as
verifyNotNullType_AT_TC_123
and the results of this method will be marked against AT-TC-123.Automation Key: The mapping of an AIO Case to an automated NUnit case can happen through a field Automation Key, which can be specified in the Case in AIO Tests app as shown below. The automation key is the fully qualified name of the test method i.e fullname from the results xml.
This can be useful at places where you do not want to add AIO case keys in the name or annotations or where automation is happening first without a manual case being created in AIO Tests.
...
Examples
Below are few examples of how to achieve mapping in various cases:
...
Code Block |
---|
[TestFixture] [Category("DDTests")] public class DataDrivenTests { [TestCase(12, 3, 4, "SCRUM-TC-13194")] [TestCase(12, 2, 1, "SCRUM-TC-13195")] [TestCase(12, 4, 3, "SCRUM-TC-13196")] public void DivideTest(int n, int d, int q, String tcId) { Assert.AreEqual(q, n / d); } } |
Info |
---|
If Case key is not provided at TestCase level and instead, is provided as Property aioCaseKey, then depending upon user’s choice at time of import, either one run would be created per data set or the same run would be updated thrice based on status and the last status update would remain. |
5. Mapping case to multiple cases
...