| || |
Certification/Process documents for testing existing software on new O/S, middleware.
Our software currently has a middleware program, but we need to create a certification process for other platforms, middleware, etc. Does anyone have documentation they could share of a certification process?
Re: Certification/Process documents for testing existing software on new O/S, middleware.
I can't share it, but I can give you the gist of it:
Enumerate system combinations;
Assign a risk score to each combination based on number of known customers using the combination, historical bug data, etc.;
Eliminate combinations with low risk scores (never enough time to do everything);
Secure system admin resources based on number of combinations;
Secure hardware resources for anticipated duration of project + some padding;
System admins begin setting up systems, letting testing group know as systems come online;
Testing group starts pounding away, letting system admins know when they can reclaim systems to set up the next combination on;
Bugs are logged, reports are distributed, determination is made to ship or hold;
If the decision is to ship, resources are released for the next project.