I had a question regarding Selenium philosophy and how the community generally implements their automated UI tests.
Let's say I had to test an app and make sure all the pages and links are working and responsive. For simplicity's sake, let's just say I'm working with 2 pages -- call them Page A and Page B.
Page A is your primary domain landing page. https://www.foo.com/
Page B is a link accessible once you are on Page A, and is generated depending on what the user inputted in Page A. https://www.foo.com/bar?param1=true¶m2=abcd¶m3=00:0001¶m4=a
Now technically speaking, an end user will never be able to reach Page B without hitting Page A. Page B's URL is generated with params depending on what the user has elected during this flow.
Test case: Verify some thing on Page B
My question: Should I be starting the test at Page A and clicking through links until I get to Page B, and do my verification when I'm there?
OR does it make sense to just start my test at Page B (with a rather obscure URL) and do my verification there by using the API to generate some crazy URL?
I'm a little torn because in my mind, "user acceptance testing" is supposed to exactly mimic a user's behavior, but starting from ZERO (Page A) for every single test seems a bit excessive in terms of time.
Thanks for your time!