Development

Design is about understanding and solving user problems. It’s about making experiences simple, accessible, and easy to use. Google states…

Professionals across various industries have historically relied on concepts to communicate and sell ideas. Concepts are very common in advertising,…

I am writing up a white paper to introduce Agile. As my role is a QA engineer working for a consultancy company.

We want customers to hire us to train them in implementing Agile and we DO want our customers to be aware of various traps when implementing Agile as well as false expectations.

I am thinking of adding some scenarios that show if Agile is not properly implemented, it may backfire on you.

Have you experienced any scenarios where Agile does not improve efficiency or even hurdle coding?

Background

We are currently moving API testing from the Technical testing team to the development team. The technical testing team has a formal process where they write the test objectives and test cases prior to developing the script in SOAPUI. Therefore, analyzing the specification and supporting requirements document are important for deriving the tests.

In the new world the developers will code/point and click their unit tests and there will be no other QA other than the UAT of the consumption of API, which can happen between a month to three months after the API has been created. The API is not an open API, only for third party suppliers and internal web and app resources.

There is an argument that additional QA work is not needed if the developers are writing the unit tests, so developers do not need to have an analysis phase or write test cases prior to setting them up in SOAPUI or coding the test.

We create enterprise level financial websites and applications. The teams is 30+ strong.

Question

Should developers still perform such analysis and write test cases?