Success Codes- Web Development Company USA Offers Web Development Success Codes web development company USA offers web development service and software development service in ASP.NET development, PHP development, Silverlight development , Flex development, SEO SEM services internet marketing services, Flash development service, search engine optimization service and search engine marketing

Success Codes

Featured Work

Our Products

  • SuccessCodes webFTP

Our Working Standards
A. Planning Phase
» Objective:
During the planning phase of the development cycle, QA team should focus on the Requirements and Business Scenarios. QA team should review these documents for their comprehensibility, accuracy, feasibility, and testability and record all issues in a “Gap Analysis on Requirements” document.
» Tasks involved:
+ Assessing the project QA effort
+ Establish defects / issues tracking methodology
+ Establish main testing approach
+ Take part in meetings with client and requirements reviews with the development team.
+ Keep meeting minutes
+ Establish the environment requirements
+ Play a development support role

» QA Deliverables:

+ Main “Bird’s Eye View” Testing Approach
+ “Gap Analysis on Requirements” document
+ Issues / Defects Tracking methodology (can be part of the Main Testing Approach)
+ Meeting Minutes

B. Design Phase
» Objective
During the Design phase, QA team should focus on reviewing and evaluating the design requirements and produce its draft Test Plan (a more refined, low-level Test Approach). During this phase, QA Team should participate in Design reviews (with the development team) and conduct gap analysis reviews on the Design requirements. All the issues should be recorded in the “Gap Analysis on Requirements” document.

The Design requirements review will help the QA team to refine the initial Test Approach and produce the draft Test Plan and the draft Test Cases structure. The draft Test Plan should define much of the detailed strategy and specific QA information that will be used for testing the application.

» Tasks involved:
+ Divide Design requirements into testable areas and sub-areas
+ Structure the draft Test Plan into testable areas and sub-areas
+ Define test strategies for each area and sub-area
+ Define list of configurations for testing

» QA Deliverables

+ Main “Bird’s Eye View” Testing Approach
+ “Gap Analysis on Requirements” document
+ Issues / Defects Tracking methodology (can be part of the Main Testing Approach)
+ Meeting Minutes

» C. Construction Phase

During the Construction phase of the development cycle, QA team should begin to execute its primary role by identifying defects and issues. At the beginning of this phase, QA team will be spending most of its time generating detailed test cases. As this phase progresses, testing will receive release candidates (modules) of increased functionality to test.

By the time the construction phase closes, then, testing team will be primarily executing test cases. C.1. Unit Testing
General Test Objectives

Unit Testing is primarily concerned with uncovering defects or logic errors in an application software component, typically a module or a screen.
The objective of the unit testing will be to assure that each component part or module of the system conforms in all aspects to the design, functional specifications and overall business objectives.

All the component or modules tested will be addressed as described in the ESD – Testing Techniques Tome document.

The exit criterion for this phase is code completion. That is, all functionality and logical and physical components of the modules must be completed and ready to interact with other modules within the application.

» Testing Techniques
Ongoing walkthroughs of modules and functions will be conducted to assure quality, consistency, accuracy, and conformance to specifications on an informal basis. A top down approach to testing will be employed.

The component will first be “black-box tested”. The focus will be the component’s functionality; Does the module / component perform the function it was designated to perform properly? Input will be varied and the results will be compared to the expected results.

The component will next be “white box tested”. The inputs will be varied in such way as to exercise as many possible entries, exits and paths as possible / relevant. The focus is to exercise all the code of the program at least once to uncover any possible errors in paths not part of the “regular” processing.

Any abnormal performance will be recorded so that when load/stress are performed later, slower processes will be already known.  
» Professionalism
We emphasize efficiency, responsibility, hard work, timeliness yet encourage creativity, teamwork and fresh vision.