Acceptance Test Procedure

Unanswered Question
Deepak kumar Mon, 03/13/2017 - 22:24
User Badges:

Hi,

Most organisations are going to have their own test plans. Consider this as a proof that you have delivered on your part of the project.


  • Basic functionality (power supplies, interfaces all working, proven over a burn-in period of say 24hrs)
  • Features (anything specific in the design, such as spanning tree state, routeing, QoS etc)
  • Performance (did the design state any expected performance, such as throughput),
  • Installation practices (racked and cabled neatly according to standards/best practice)
  • Integration (anything it is connected to interoperates as expected)
  • End to end test (may require application staff to perform testing) while
  • Caveats, errata, logs all reviewed and confirmed as non-impacting.



This is not an exhaustive list but gives you somewhere to start.

Regards,

Deepak Kumar

Actions

This Discussion