![\"image](\"\/blog\/wp-ttn-blog\/uploads\/2016\/01\/image-3.png\")
<\/p>\nAs the requirements in subsequent development cycles are shared over email or on calls, hence, they tend to get scattered. Insufficient requirements also add to this problem. Lack of documentation asks for a smarter way to collate and translate the requirements into testing artifacts such that they don\u2019t get missed out.<\/p>\n
Hence this blog is an attempt to share some practices which helped me to understand software requirements.. These methods or practice can be very helpful and effective and we can follow them when we find that requirement is not sufficient enough to proceed with testing.<\/p>\n
<\/p>\n
Translate available Requirements to Test Cases:<\/strong> Attend team meeting and client meetings:<\/strong> Refer other similar apps in market:<\/strong> Explore the software:<\/strong> Hints and hacks:<\/strong><\/p>\n \u2022 Always inform team and stakeholders about the risks. As the requirements in subsequent development cycles are shared over email or on calls, hence, they tend to get scattered. Insufficient requirements also add to this problem. Lack of documentation asks for a smarter way to collate and translate the requirements into testing artifacts such that they don\u2019t get missed out. Hence this blog is […]<\/p>\n","protected":false},"author":489,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":6},"categories":[1817,1772,1,1816],"tags":[3026,3025,3027,3024],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/31823"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/489"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=31823"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/31823\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=31823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=31823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=31823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nStart with whatever requirements you have:<\/strong>
\nExplore and understand the available requirements first, Work with whatever little documentation you have in your plate. You can use client emails and his previous feedback (if any), and whatever documents are available. Understand the requirements and note down the queries and clarify them with stakeholder. Ask for application flow diagrams and wireframes for better understanding of the requirements.<\/p>\n
\n\u2022 After understanding the available requirements create all the possible test cases.
\n\u2022 Emails, Notes, Recorded issues and marketing materials can be used to create test cases.
\n\u2022 Document on a high level first and keep adding the details as you proceed.
\n\u2022 Add more details while testing, connect high-level requirement and detailed test scenarios.<\/p>\n
\nActively participate in the team meeting and discuss your queries in the meeting. Raise your concerns and feedback about the app to the entire team. Attend client interactions, observe his approach and his requirements what he actually wants in the app. Create notes of the call and share it with team time to time. Time to time interaction with team and client will help tester\u2019s to get better idea and clarification on the queries. It\u2019s a good platform to raise queries and concerns.<\/p>\n
\nIn this wide market many options are available for users. User is not dependent on one app. We can use these aps for our advantage; we can refer other similar apps available in the market. Testers can write high level test cases using the application as a reference. Referred application might have some bugs for e.g. In an online shopping app after registration it takes user screen 1 then never assume that it is correct behavior. Never assumes things observe the scenarios carefully and for doubts always take help team for clarification.<\/p>\n
\n\u2022 Perform the exploratory testing on the project. Exploratory testing is about exploring, finding out about the software, what it does, what it doesn\u2019t do, what works and what doesn\u2019t work.
\n\u2022 The tester is constantly making decisions about what to test next and where to spend the (limited) time. This is an approach that is most useful when there are no or poor specifications and when time is severely limited.
\n\u2022 Think from the user\u2019s perspective and try to observe things as user.
\n\u2022 Try to explore most critical and high use features.
\n\u2022 Focus on the features which will be released soon.
\n\u2022 Learn the software behavior.
\n\u2022 Learn users, objects, workflows, product properties.
\n\u2022 Explore competitor\u2019s product.<\/p>\n
\n\u2022 You cannot test everything \u2013test by priority.
\n\u2022 Discuss doubtful issues.
\n\u2022 Always follow up discussion with written notes.
\n\u2022 Keep calm and Test, Test again then test some more.<\/p>\n","protected":false},"excerpt":{"rendered":"