List of requirements and checklist in all the stages of testing

I guess most of you would have missed some important task which should have been done earlier before starting to test. To be open I had came across such situations many times. In order to overcome this, I am creating the checklist for all the tasks in the testing phase. For now I have added few and will keep adding the details. Follow this blog or bookmark it to your favorites to see the updates.

To start building our integration test environment.


Testability requirements

  • All applications that exists or to be delivered in the production have to be available or simulated in the test environment. 
  • Getting the list of settings and configurations is available along with the comparisons of the settings and configurations of the production environment is necessary.
  • Get the required tools and licenses ready for testers (If tools can not be provided due to licensing issues, try to put in a work-around is in place to facilitate testing)
  • If the application is going to use any front end devices to access software through different channels (like phones, card readers, GPS Units, desk tops, laptops, pads,...) get that in place
  • Batch procedures are internally controllable and automated as in a production environment (manual trigger, start, pause, stop batch procedures)
  • Measuring tools should be in place to enable monitoring the communication between applications and application layers.
  • External Connectivity to test environments for support, deployment and testing should be ready
  • Database read access is required for all testers
  • Make sure that the Input/output simulators are in place and documented for every interface type
  • At least 1 test user exists for every defined role in the application under test
  • Time traveling is possible in at least one of the following means: "time goes by faster (eg: 1 week = 1 hour)", "move forward and reset from a defined time in the future", "coherent data creation/update to a  time stamp in the past"
  • All configurations of the different interfacing systems within the test environment have to be centrally managed
  • The test infrastructure has an availability of 95% (planned deployments are not included)
  • Defects are centrally managed, using 1 agreed defect managing system and flow 

I would highly recommend you all to have a look at the other requirements, which I have prepared. 
The checklist of Test data requirements -  Test Data Requirements
The checklist for Deployment/Release management requirements -  Deployment or Release management requirements
The checklist for Maintainability requirements - Maintainability requirements

Join our community in Facebook and Google+ at the below URL's to stay up to date:





1 comment:

  1. An outstanding share! I have juѕt forwardeԁ thiѕ onto а
    cо-worker ωho waѕ сonԁucting a little resеаrch on
    this. Anԁ he in fact orderеd me breakfast sіmply becausе I stumbleԁ upon іt fоr him.
    .. lol. Sο allow me to reworԁ this.

    ... Τhanks fοr thе meal!! But yeah,
    thanx fοr spending the time to diѕcuss this topic
    here on yοur site.
    my webpage :: bd web searh

    ReplyDelete