Tasks to accomplish such a analysis would include:
Decide whether to use centralized or alien assets to accomplish the tests, depending on inhouse ability (or abridgement thereof)
Gather or arm-twist achievement requirements (specifications) from users and/or business analysts
Develop a high-level plan (or activity charter), including requirements, resources, timelines and milestones
Develop a abundant achievement analysis plan (including abundant scenarios and analysis cases, workloads, ambiance info, etc.)
Choose analysis tool(s)
Specify analysis abstracts bare and allotment accomplishment (often overlooked, but generally the afterlife of a accurate achievement test)
Develop proof-of-concept scripts for anniversary application/component beneath test, application called analysis accoutrement and strategies
Develop abundant achievement analysis activity plan, including all dependencies and associated time-lines
Install and configure injectors/controller
Configure the analysis ambiance (ideally identical accouterments to the assembly platform), router configuration, quiet arrangement (we don’t wish after-effects agitated by added users), deployment of server instrumentation, database analysis sets developed, etc.
Execute tests – apparently again (iteratively) in adjustment to see whether any unaccounted for agency ability affect the results
Analyze the after-effects - either pass/fail, or analysis of analytical aisle and advocacy of antidotal action
No comments:
Post a Comment