| || |
Automated API Regression Pack
I have tasked one of my team to create a automation regression pack to test a Rest API. We have attempted to do this in the past and encountered some problems so Im looking for some advice from the testing community on this forum. Hopefully the questions below will get a conversation started. Any advice will be great, thank you in advance!
The business I work for provides a portal to manage accounts (saas), therefore a lot of the teams time is spent setting up test data before we can start testing any new features. The portal sits on top of an API which is the AUT (we are testing the API), (this is not unit testing).
We are looking to use Selenium/Rspec/Test-Unit for the testing.
Should we be looking to create test data using the API (i.e create users and accounts using the API) or would it be safe to write DB inserts to setup the test data. My initial concerns with inserts is that we are not using the system to create the data and consequently the data being inserted may not be realistic although we would endeavour to make sure it is?
The core language of the API is written in PHP. The test team uses Ruby for obvious reasons (online community support/ Selenium support). Is there any justification to move to PHP. This will involve a large learning curve for QA and UI and API test being written in different languages.
How strict should the API tests be? obviously if we write strict tests then they are more likely to break and theres likely to be more false negatives in terms of tests failing. Whats is the usually pay off for this scenario. Stricter and better test with a lotto overhead or not as strict tests but more reliable; and less maintenance.
What steps can we take to ensure that the the test that we write are as fast as possible, I appreciate that this is a open question.
Response Inlined with >>>
Originally Posted by testeverything