Various types of testing required for e-commerce site include:

1. Developer Tests:
2. It can be referred to as code level tests performed by developers of modules.
3. It is the act of regression testing source code by developers. This is sometimes called "unit regression testing" but many developer tests go beyond unit testing to address integration testing as well.
4. Some important philosophies with respect to developer testing are as follows:
   • The goal is to find defects.
   • Test early and often. The cost of change rises exponentially the longer it takes to find and then remove a defect.
   • Test to the risk. The riskier something is, the more it needs to be reviewed and tested.
   • Validate all the artifacts. Test all the artifacts, not just the source code, although the focus of this guidance is testing code.
5. Feasibility Testing:
6. This type of testing tests a new approach, often near the start of a project to make sure it is acceptable in terms of user experience.
7. The feasibility test brings in a series of practical constraints by asking whether the selected alternative can be implemented given time, financial, legal, personal, and social constraints.
8. By focusing the decision-maker on these constraints, the feasibility test helps to integrate ethical considerations with other aspects of a decision.
9. Thus, it is an operation plan review criteria whether or not a plan is within capacity of the resources that can be made available.

10. An analysis and evaluation of a proposed project to is done to determine if it is technically feasible, if it is feasible within the estimated cost, and if it will be profitable.

11. Module Testing

12. This type of testing checks individual modules have the correct functionality.
13. Testing is basically done to check for correct outputs for specified inputs.
14. It is the testing of complete code objects as produced by the compiler when built from source.
15. The testing can be done in the target system, an emulator, simulator or any other suitable test environment.

16. The branches and paths in functions and modules have to be considered and when the tests will be designed not only the function of the test object is tested, but at the same time it will be checked if all branches in the software have been covered.

17. Integration Testing

18. Basically it checks interactions between groups of modules.
19. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.
20. The purpose of integration testing is to verify functional, performance, and reliability requirements placed on major design items.
21. Top down and bottom up are two approaches of Integration testing.
22. Bottom up testing is an approach to integrated testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

23. Top down testing is an approach to integrated testing where the top integrated modules are tested and the branch of the module is tested step by step until the end of the related module.

24. System Testing

25. They basically check interactions between all modules in the system.
26. This testing is conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements.
27. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.
28. The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the hardware.
29. System testing tests not only the design, but also the behaviour and even the believed expectations of the customer.
30. Performance Testing
31. Performance testing tests the speed of the system under high load.
32. It is in general testing performed to determine how a system performs in terms of responsiveness and stability under a particular workload.
33. This load can be the expected concurrent number of users on the application performing a specific number of transactions within the set duration.
34. This test will give out the response times of all the important business critical transactions.
35. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.

The tools used for website development and testing are as follows:

1. Basic text and graph editors like Program File Editor (PEE), Adobe Photoshop etc.
2. Specialized HTML editors like Arachnoid.
3. Site Management tools like Cold Fusion, Dream Viewer etc.
4. Content Management Systems like RedDot, InterVowen etc.
5. E-commerce site development tools like Actinic, Intershop etc.