Vous êtes sur la page 1sur 2

Testing Strategy

The purpose of the Testing Strategy is to define the overall context for the entire testing process. The process is
different depending on the specific characteristics of your solution. In many respects, this is the most important
part of the testing process, since all future testing decisions will be made within the context of the strategy. Here
are the basic parts of the testing strategy:

Project Overview

Business Risk

Testing Method

Testing Approach

Testing Environment

The Testing Strategy should be written at a high level so that it can be read and understood by the customer. Since
all future testing decisions are based on the strategy, the project sponsor and other major stakeholders should
approve this document.

Key points

 If you are working on a large project, you need to formulate an overall Testing Strategy during the analysis
phase. The Testing Strategy defines the overall approach to testing and describes how the testing process will
ensure that the solution has the appropriate level of quality and reliability.
 The Testing Strategy provides the overall guidelines from which all future testing decisions are made. A well-
crafted Testing Strategy allows the rest of the testing process to be defined more effectively.
 The Testing Strategy needs to be understood and approved by the sponsor. If the strategy is accepted, there is
a much better likelihood that the final solution will meet the customer’s expectations.

The areas covered by a strategy will vary depending on the size of organisation and nature of the software testing
undertaken however, here is a list of suggestions for the areas you may want to consider:

 Introduction and objective of the strategy document.

 An explanation of your testing philosophy or ‘mission statement’.
 Responsibility for ownership and sign-off of the strategy.
 Who the document is aimed at and how they should use it.
 An overview of your testing methodology (e.g. V-Model) and how this fits into the overall project development
 A list of Test Phases to be considered for each project e.g. Unit Testing, Integration Testing etc.
 An overview of the process followed and deliverables produced (e.g. test plans/scripts/handover criteria) from
each test phase and who is responsible for these.
 Testing waiver process i.e. what happens and who needs to agree when a test phase which would normally be
included in a project is being waived.
 Constraints of the current test environment and longer term plans to overcome these.
 Accepted and agreed risks associated with your testing and any mitigating factors.
 Current known Issues associated with testing and plans to overcome these.
 Any long term plans for process improvements (e.g. plans to automate testing) and the deadlines associated
with these.
How to find open ports on a computer

To find open ports on a computer, you can use netstat command line.

1. To display all open ports, open DOS command, type netstat and press Enter.
2. To list all listening ports, use netstat -an |find /i "listening" command.
3. To see what ports your computer actually communicates with, use netstat -an |find /i
4. To find specified open port, use find switch. For example, to find if the port 3389 is open or not,
do netstat -an |find /i "3389".
5. You can use PULIST from the Windows Resource Kit to find which process is using a specified
port. For example, pulist |find /i "4125" may display

Process PID User

mad.exe 4125 Chicagotech/blin

Or you can use tasklist to find PID.

Resolution: Run netstat -a command that will shows all active ports.

Popular Port #. FTP: 21. Telnet: 23. SMTP: 25. HTTP: 80. POP: 110. HTTPS: 443 ...

http://www.ipchicken.com/ To know about your External Ip address