Testing Without Requirements

Who hasn’t been in the situation where a user story or ticket has no description or requirements 🤷🏽. I know, we all have been there! But what can you do in order to test something to add value to a team? There are different types of them, from system requirements to regulatory requirements.

But have you also heard already about explicit and implicit requirements and why they are important to know? Especially, software testers have to deal with both on a daily basis and therefore, it’s important to understand them and how to handle them. And do you also know what to do, when there are no requirements in a ticket, but you have to test the product? If not, then take a look at the following video to learn all about it.

Please check the video description for more links for you to follow up. Leave a like and comment at the video to support me. Don’t forget to subscribe to my channel to not miss any new videos.