POP UX

My usual approach to testing an application is to test it by performing the task the application is intended for.

For example, I am now working on a coaching application. My usual strategy is to sign up for the application as a coach, then imagine what tasks/procedure a coach will perform using the application. I will then perform them step-by-step, and at the same time do bug test. I kind of notice that the application is quite big that it performs a lot of tasks, major tasks. Looking at the different functions of the application, I realized that aside from testing step-by-step, splitting the application into its major functions will make the testing more smooth and manageable. I will not be overwhelmed with the complexity and its very wide scope.

Determining the different major modules/functions is not that easy also, it is not automatic (for me). It took time before I was able to pinpoint the different major functions. Another advatange of being able to split the application into smaller modules is that you get to know it in an intimate level, which makes tracing dependencies and interwoven functions easier.