Online Resource for Software Testing A blog cotaining information regarding Software Testing and Quality Assurance, along with interview questions and answers Statistics Unique Visitors: Total Unique Visitors: Outgoing: Total Outgoing: 157 0 47 1967

Articles from Online Resource for Software Testing

Responsibilities of a Test Manager 2005-11-14 09:24:00 Responsibilities of a Test Manager: ? Manage the Testing Department. ? Allocate resource to projects. ? Review weekly Testers' status reports and take necessary actions ? Escalate Testers' issues to the Sr. Management. ? Estimate for testing projects. ? Enforce the adherence to the company's Quality processes and procedures. ? Decision to procure Software Testing tools for the organization. ? ...

Responsibilities of a Test Lead 2005-11-11 09:26:00 Responsibilities of a Test leader: ? Prepare the Software Test Plan. ? Check / Review the Test Cases document – System, Integration and User Acceptance prepared by test engineers. ? Analyze requirements during the requirements analysis phase of projects. ? Keep track of the new requirements from the Project. ? Forecast / Estimate the Project future requirements. ? Arrange the Hardware and ...

Boundary Value Analysis (BVA) 2005-11-08 09:45:00 Boundary value analysis is a technique for test data selection. A test engineer chooses values that lie along data extremes. Boundary values include maximum, minimum, just inside boundaries, just outside boundaries, typical values, and error values. The expectation is that, if a systems works correctly for these extreme or special values, then it will work correctly for all values in between. An ...

The Testing Estimation Process 2005-10-28 09:36:00 One of the most difficult and critical activities in IT is the estimation process. I believe that it occurs because when we say that one project will be accomplished in such time by at such cost, it must happen. If it does not happen, several things may follow: from peers’ comments and senior management’s warnings to being fired depending on the reasons and seriousness of the failure. Here are a ...

Testing - when requirements are changing continuously 2005-10-21 14:30:00 Work with management early on to understand how requirements might change, so that alternate test plans and strategies can be worked out in advance. It is helpful if the application's initial design allows for some adaptability, so that later changes do not require redoing the application from scratch. Additionally, try to... - In the project's initial schedule, allow for some extra time to ...

Difference between Verification and Validation 2005-10-17 09:20:00 Verification ensures the product is designed to deliver all functionality to the customer; it typically involves reviews and meetings to evaluate documents, plans, code, requirements and specifications; this can be done with checklists, issues lists, walkthroughs and inspection meetings. You CAN learn to do verification, with little or no outside help. Validation ensures that functionality, as ...

Difference between Alpha and Beta Testing 2005-10-14 09:40:00 Alpha testing is final testing before the software is released to the general public. First, (and this is called the first phase of alpha testing), the software is tested by in-house developers. They use either debugger software, or hardware-assisted debuggers. The goal is to catch bugs quickly. Then, (and this is called second stage of alpha testing), the software is handed over to us, the ...

How do you execute tests? 2005-10-13 09:48:00 Execution of tests is completed by following the test documents in a methodical manner. As each test procedure is performed, an entry is recorded in a test execution log to note the execution of the procedure and whether or not the test procedure uncovered any defects. Checkpoint meetings are held throughout the execution phase. Checkpoint meetings are held daily, if required, to address and ...

How do you create a test plan/design? 2005-10-12 09:14:00 Test scenarios and/or cases are prepared by reviewing functional requirements of the release and preparing logical groups of functions that can be further broken into test procedures. Test procedures define test conditions, data to be used for testing and expected results, including database updates, file outputs, report results. . Test cases and scenarios are designed to represent both ... Design

How do you create a Test Strategy? 2005-10-11 10:41:00 The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment. ...

What is software testing methodology? 2005-10-10 12:36:00 A software testing methodology is the use of a three step process of: 1. Creating a test strategy; 2. Creating a test plan/design; and 3. Executing tests. This methodology can be used and molded to your organization's needs. Using this methodology is important in the development and in ongoing maintenance of the customers' applications. ...