Skip to main content

Had you to design test cases for a complex feature. What factors did Tester consider, and how did prioritize test scenarios?

Image
By

  Take an instance as new application has integrated into existing applications(i,e., Running on real time )Customer want to integrate their application into third party vendors in order to let the customer order their needs through our created app itself.

Factors Consisdered : Error Handling , Functional Requirements , Edge cases , Non-Functional Parameters .

Transaction Flow

Flow1: Customer Land on third party vendors app and start picking their items.

Flow2 : Picked Items has to go Cart Page and can see number of items added by visually.

Flow3: Once click to checkout , it will allow the user to input their card details and processing transaction.

Flow4:Once Transactions done, newly created app show the details of the order and online tracking number .


Prioritize scenerios based on the Business Emergency and needs ,well in briefly communicate to team members to identify the Critical paths and prioritize the that test suite first and Start  the execution based on what need to tested first and make it ready for next sprint.

Comments

Post a Comment

Popular posts from this blog

A Well Comprehensive Test plan for Manual Testing

By
  Scope Definition: Define the scope based on specifications and requirements provided. However, also include exploratory testing to uncover issues that might not be explicitly mentioned in the requirements. Consider factors like usability, accessibility, security, and performance to broaden the scope beyond just functional testing. Considering factors like usability, accessibility, and security in the scope definition is essential for ensuring a comprehensive testing approach that goes beyond functional requirements Test Case Design: Use a combination of traditional methods like boundary value analysis, equivalence partitioning, and decision tables for structured testing. Incorporate exploratory testing techniques to explore the application and identify unexpected behaviour or edge cases. Prioritize test cases based on risk assessment and criticality. can implement the shift-left approach in...
Post a Comment
Read more

Essential of Creating Test plan in Testing

By
  Why Test Plan is Vital Document! Test Planning process and plan itself serve as vehicle for communicating with other members of the project team, tester, Dev, BA, Peer and other stakeholders. This communication allows the test plan to influence the project team and allows the project team to influence the test plan. We can accomplish this Communication through circulation of one or more test plan drafts and through review meeting. E.g.: Please tell me what the plan is for releasing the test items into the test lab for each cycle of test execution E.g.: Please let me know which version of the test tool   will be used for the regression tests of the previous increment. A test plan Document becomes the record of previous discussions and agreements. Test Plan helps us to Manage the change if you are in Agile , have to this as Handy. Ways to write a Test Plan Document. Analyze the Product: Understand the product's objectives, target users, specific...
Post a Comment
Read more

How test steps and Expected result and actual result should get differ each other and be unique?

By
  Test steps are action-oriented and describe the registration process, the expected result outlines the desired outcomes, and the actual result provides observations on what actually occurred during the execution of the test case.   Each section serves a unique purpose and together forms a comprehensive test case.  Any discrepancies between the expected and actual results can be easily identified and addressed . Test steps, expected results, and actual results in test cases should be distinct and unique to provide clarity, avoid ambiguity, and facilitate effective communication between testers and other stakeholders. Here are some guidelines on how to make them differ and unique: Test Steps: 1. Sequential and Clear: • Test steps should be listed in a sequential and clear manner.  • Each step should represent a specific action that the tester needs to perform. 2. Action-Oriented: • Use action-oriented language in test steps.  • Clearly state what actions ...
Post a Comment
Read more