1

I'm now doing a test plan for an app total revamp. The testing will include both functional(if it works according to plan, no errors, doesn't break) and usability(if it's intuitive, if the wayfinding is clear, if key actions are clear).

We have a short testing window and it can feel overwhelming as there are so many scenarios to account for.

I'm considering ditching the UX testing and simply do the functional testing as the UX iteration can be done after launch, but if the system doesn't work functionally we can't even launch.

Has anyone been in this situation before? And how did you overcome it? Are there any resources that helped?

1
  • 1
    It depends. Are you using a waterfall approach, where everything is developed before testing is done? Are GUI parts being designed in a tool that would allow for testing before handing over the spec to development? If you’re in an agile context, it’s weird that you’re working on a plan already, and it’s a tough question. My personal opinion is that it’s very important for everyone to gain confidence in the agile process and get something valuable into the hands of users as fast as possible. A prototype isn’t valuable. Agile needs refactoring, and fixing usability issues is part of that.
    – Andy
    Sep 14, 2023 at 12:36

1 Answer 1

0

If you think of testing as a separate part of the overall project delivery activity, and something that you simply need to tick off as part of the release process, then it would feel like something that is added on rather than built into the project timeline and budget.

Also, you should think of user experience to be inclusive of the functional and non-functional aspects of the product, but obviously the functional requirements need to be met as a minimum (or pass the test) before you can deal with fine-tuning the actual experience (rather than usability aspects) of the product.

It isn't exactly clear what your role is, but hopefully a test plan is developed with the development team in mind so that it addressed both functional and non-functional aspects of the user experience over the lifetime of the product and/or release cycles.

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.