During this phase, Teklead personnel will execute functional, integration, system, end to end, performance, and volume test cases. We will find and track bugs and then retest the fixes.


Teklead’s Test Strategy is encompassed by the Test Method, Test Plan, Test Cases, Test Environment and Test Data. In a nutshell, this presents the type of testing that will be done during this phase – functional, data, front end, back end, middleware, upstream, downstream, etc – in addition to how much testing will be done, entrance and exit criteria, start and end time, effort of testing and time frame, and the environment in which testing will be done.

Once the testing strategy is defined, our goal is to automate as much of the software as possible – if it can be automated – to save time and money. In order for this to be possible, Unit Testing by the Development team must be done first, followed by Functional Testing by the Functional / Manual QA team before it can become a candidate for automation. Automation can further be broken down by the type of testing that is done (e.g. functional automation, shell scripting, and backend DB automation).


Various automation tools help test across the end to end spectrum of the application’s SDLC. For example: Python, PHP, SQL, JavaScript, Watir, Redis, Selenium, RUBY, JSON, XML, Unix Shell Scripting, HP tools, QTP, ALM, IBM Rational Suite, Oracle Testing Suite.


Our testing staff structure is set up as a 3:1 or 2:1 ratio of Developers to QA personnel, ensuring the best possible results for your project. With regards to onshore, near shore and offshore, the idea is that we get 24-hour support across all of our product lines.

For example: if our testing center is in New York, our near shore should be 3 to 4 hours behind the local New York time. Thus, work is always possible and support is always accessible. Additionally, when the near shore team finishes their day, the offshore team starts their day. This workload overlap helps attain maximum testing results and turnaround times.