Day: October 28, 2020

All components of an IT ecosystem need testing and validation. Any professional, or student in MIS, knows this, of course. What is harder is determining how to approach a given modification and the testing needed in a pragmatic fashion. There is a process that can be applied to most initiatives that consist of planning, analysis of the context, definition of tasks, estimation of effort, and risk mitigation.

When we address what needs to be delivered in a pragmatic sense, the priorities are easy to see. Once we start into a project we can get lost in complexity, engineering principles, etc. In order to make QA/Testing accessible, scalable, and reusable, it is best to drill down the process into checklists for procedures. Every organization has someone who knows what they need the system to do – from an admin who gets how to connect the ports, to the AP person who can process a check before we say “deposit”, to an EDI coordinator who knows the JIT threshold. Determining the best way to test usually involves understanding the actual job we need to accomplish and taking the time to break into steps where failure can be determined.…