0

I have always done these very simple test cases so I am actually very lost and got overwhelmed when I got this assignment where I should do test cases from a functional design specification document. Of course you have your introduction and purpose then there are different section and the section themselves have sub-sections (3.1, 3.2). One of the functions being example search, add, edit and remove in shopping cart on the website and other for an app. And then there is attachment with pictures of the prototypes showing these functions, diagrams, additional/subblementary specification, UI etc. It's a lot!

I don't really know how to tackle these. If I were to write for test cases for each subsection, I think there would be alot. How do I need to think and go about solving this? This might actually sound easy to many of you but I just started with testing (7 month ago). This is really interesting.

1 Answer 1

0

As an outsourced software testing organization, writing a test case w.r.t. FIGMA or Design Steps for both Web and Mobile apps requires a lot of brainstorming. Hence as per my experience and recommendation:

  1. Create single test case each for functional test cases i.e. for major functionalities/application workflows. However, when you create a TestRun --> at that point select the test cases in both test runs say for Web and iOS as the core application functionality is same.
  2. Additionally for UI test cases, create one test case each for individual screens and attach the screenshots in a TestRun for reference so that can be viewed while you are executing the tests.
1
  • Thank you! so its fine doing testcases for each then! But how would I do a testrun when the app and website in the document does not exist?
    – AlwaysNew
    Commented Jun 24, 2022 at 18:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.