Number of Tests
We have a service that returns a huge order object/xml. Does anyone know of any documented strategies or methodologies for narrowing down the # of tests necessary? Is it normal to test every element...
Forum Discussion
Understand your perspective. I see this is subjective, depends on various reasons and test coverage should be atleast, and add tests to increase possibility to break the service/application rather than based on just number of tests.
1. verified uses cases that particular service/operations supports and they work
2. tests must cover as per the documentation of service, response codes etc
3. how the application works if any of the mandatory elements missing, i mean identify certain pattern and test those. It is not much fruitful results applying the same pattern to each of element, in the end probably get same kind of response. Of course, that does mean optional elements can be ignored. See if the default value mentioned for the optional elements working as expected etc
4. Check if there are any enumerations that any elements follows/uses, try to break there if allows other than intended values for that specific elements.
5. If there are some choice elements in the request, cover possible both options.
6. Add boundary conditions
Some of my inputs i could think of, I am sure you can come up some more. Hoping that understanding the wsdl/underlying xml schema would help you well to draw the tests.
1. verified uses cases that particular service/operations supports and they work
2. tests must cover as per the documentation of service, response codes etc
3. how the application works if any of the mandatory elements missing, i mean identify certain pattern and test those. It is not much fruitful results applying the same pattern to each of element, in the end probably get same kind of response. Of course, that does mean optional elements can be ignored. See if the default value mentioned for the optional elements working as expected etc
4. Check if there are any enumerations that any elements follows/uses, try to break there if allows other than intended values for that specific elements.
5. If there are some choice elements in the request, cover possible both options.
6. Add boundary conditions
Some of my inputs i could think of, I am sure you can come up some more. Hoping that understanding the wsdl/underlying xml schema would help you well to draw the tests.