A test plan is a tool you use while planning a period of testing. It basically describes what will be tested, who will do it, where they will do it, and how they plan on doing just that. In some coorperations, where law and contracts are really important, test plans are usually the size of a small child, and nobody ever reads it. Apart from lawyers. That's because test plans aren't always made for you - they can also be made for your team or for different stakeholders.
I've made a series of test stories from my favorite test runs. During this test run I cooperated with a company's designer to construct an optimal task flow in an app. In the end I drew a complete set of wireframes for the app that the developer used for the development process.
I've made a series of test stories from my favorite test runs. This 2-days user experience test run is without a doubt the most extensive test I ever did in the smallest amount of time. These were not average 8-hour workdays, these were meticulously planned sessions that fit into my timetable with great precision and lasted from morning to evening.