Forum Discussion

TanyaYatskovska's avatar
TanyaYatskovska
SmartBear Alumni (Retired)
6 years ago

[Day 4/5] APIvsUI Testing - What is your ideal API testing process?

Hi Guys,   I hope you enjoy the conversations we are having at the API Testing vs UI Testing competition. The UI Team has a bit more points at the moment. However, I’m sure you can easily catch t...
APIvsUI
avidCoder's avatar
avidCoder
Super Contributor

In my daily software testing life cycle, I am using below approach before I start testing any AUT:-

 

  1. Gathering the requirement to test any modeules.
  2. Breaking the application under test into smaller modules.
  3. Writing the testcases.
  4. Making the testcases available before the developer starts coding.
  5. Grouping the testcases for regression testing.
  6. Maximizing the test coverage.
  7. Conversation with the developers.
  8. Don't let the developers to test their own code. unless, it is unit testing.
  9. Use the bug reporting tool sich as Rally, JIRA, HP-ALM
  10. Write clear, descriptive and unambigous bug report.

Basically, I change the testing process everyday based on the testing requirements.

And when it comes to measurement of testing process. We and the team use SalesForce for this purpose. It allows you to build personal dashboard for a business as a whole or every single employee in your business. 

 

If you want to make sure that every team members stay focussed on the most important business metrics, there is no better solution than salesforce.

nmrao's avatar
nmrao
Champion Level 3
6 years ago
May not agree with #8, avidCoder. How is possible to get the quality code unless develop tests his own code?
  • avidCoder's avatar
    avidCoder
    Super Contributor
    6 years ago

    nmrao I mean to say here is, the developers can test their own code using UNIT testing. Whatever they do. After that all the other types of testing should be done by testers only. 

     

    And, I have changed the sentence. 

    • avidCoder's avatar
      avidCoder
      Super Contributor
      6 years ago

      And also, Developers normally work with the developer mindset of "how to make this work?". A good tester is thinking about "how to break this?" - a very different mindset. Unit testing and TDD does teach developers to change hats to some extent. Moreover, there can be a possibility of misunderstanding requirements. Therefore final acceptance tests should be conducted by someone as close to the client as possible.