Testing Methods and Tools
Testing Methods Used in IT Six
By the developers:
- Unit Testing: It is sometimes called "Component Testing" and involves checking that each feature specified in the "Test Design" has been implemented in the development of component code. Developers usually carry this out, as they understand best how a component works. A component performs only a small part of the functionality of a system and it relies on co-operating with other parts of the system.
- Integration Testing: The interfaces between the modules or system components and the usage of global data and shared resources are tested to verify the components are compatible with one another and constitute a testable system.
By the QA/testing team:
Testing covers Equivalence Partitioning, Boundary Value Analysis, Cause-Effect Analysis and Logic.
Types of testing performed:
- Installation Testing
- Functionality Testing
- Compatibility Testing
- System Integration Testing
- Performance Testing: Stress Testing, Availability Testing, Response/Load Testing, User Interface Testing, Security Testing
- Regression Testing
- Recovery Testing
- Acceptance Testing
Testing Workflow
- Analyzing the functional requirements and documentation of the application under test
- Test Plan development
- Test Case and/or Test Script development
- Test Plan execution
- Defect reporting
- Generating bug report and metrics for the executed tests
The testing practices inside IT Six are IEEE and ISTQB compliant.
The Test Plan prepared for every project details specific processes, including the testing strategy, features to be tested, test approach, resources, testing schedule, environmental requirements, risks/dependencies etc.
Our transparent approach enables customers to have online access to the QA system, in order to track the status of the project throughout the entire life cycle.
The testing process involves the following activities:
- Understanding and reviewing requirement specifications
- Creating Software Test Plan
- Creating detailed test cases
- Creating test data
- Setting up the test environment
- Executing tests
- Managing defects
- Analyzing results
Automation testing process:
- Defining test framework
- Creating automation test cases
- Setting up the test environment
- Creating test scripts and test data
- Defining reporting mechanism/system for test runs
- Carrying out test runs in different environments
- Analyzing results
Testing Tools
The following tools are used at IT Six to carry out testing effectively:
- Defect Tracking Tools
- Bugzilla
- Mantis
- Jira
- VersionOne
- trac
- Test Case Management Tools
- TestLink
- VersionOne
- Test Director
- Automation Testing Tools
- QTP
- WinRunner
- AutoIt
- In-house scripts/utilities
- Performance / Load Testing Tools
- JMeter
- OpenSTA
- Load Runner
- MS Web Application Stress Tool
- In-house scripts/utilities
- Virtualisation
- VMWare Workstation
- VMWare Server
- Other Tools
- AppScan
- Process Explorer
- FxCop
- JProbe
- WebScarab
- Boundschecker
- Fitnesse Xenu
- LinkScan
- HTTPWatch
- SnagIT
- JAWS
- Netcat
- XML Spy
- Ghost
- DameWare
- PCAnywhere
- RDP
- VNC
- Putty Xmanager
- Ethereal
- Syslinux
- NmapExceed
- GoToMeeting
- GoToAssist



