Priority of Bug

Posted On 08 December, 2008 at 9:51 PM by Rajeev Prabhakaran

Priority indicates how important it is to fix the bug and when it should be fixed
Immediate Priority: The bug is of immediate priority if it blocks further testing and is very visible
At the earliest Priority: The bug must be fixed at the earliest before the product is released
Normal Priority: The bug should be fixed if time permits
Later Priority: The bug may be fixed, but can be released as it is

Posted in Labels: | 0 comments

Severity of Bug

Posted On at 9:47 PM by Rajeev Prabhakaran

Bugs Severity indicates how serious the bug is and reflects its impact on the product and customers of the product. It can be critical, major, minor, cosmetic or suggestion.
Critical severity: The bug is of critical severity if it causes system crash, data loss or data corruption.
Major severity: The bug is of major severity if it causes operational errors, wrong results and loss of functionality.
Minor severity: The bug is of minor severity if it causes defect in user interface layout or spelling mistakes.

Posted in Labels: | 0 comments

Black Box and Functional Testing

Posted On 07 December, 2008 at 10:07 PM by Rajeev Prabhakaran

Black Box Testing is testing without knowledge of the internal workings of the item being tested. The Outside world comes into contact with the test items, only through the application interface, an internal module interface, or the INPUT/OUTPUT description of a batch process. They check whether interface definitions are adhered to in all situations and whether the product conforms to all fixed requirements. Test cases are created based on the task descriptions
Black Box Testing assumes that the tester does not know anything about the application that is going to be tested. The tester needs to understand what the program should do, and this is achieved through the business requirements and meeting and talking with users.
Functional testing: This type of tests will evaluate a specific operating condition using inputs and validating results. Functional tests are designed to test boundaries. A combination of correct and incorrect data should be used in this type of test.

Posted in Labels: | 0 comments

Scalability and Performance Testing

Posted On at 2:15 PM by Rajeev Prabhakaran

Scalability and performance testing is the way to understand how the system will handle the load cause by many concurrent users. In a Web environment concurrent use is measured as simply the number of users making requests at the same time.
Performance testing is designed to measure how quickly the program completes a given task. The primary objective is to determine whether the processing speed is acceptable in all parts of the program. If explicit requirements specify program performance, then performance test are often performed as acceptance tests.
As a rule, performance tests are easy to automate. This makes sense above all when you want to make a performance comparison of different system conditions while using the user interface. The capture and automatic replay of user actions during testing eliminates variations in response times.
This type of test should be designed to verify response and execution time. Bottlenecks in a system are generally found during this stage of testing.

Posted in Labels: | 0 comments

System Testing Check List

Posted On 05 December, 2008 at 6:46 PM by Rajeev Prabhakaran

  1. Run time behavior on various operating system or different hardware configurations.
  2. Install ability and configure ability on various systems
  3. Capacity limitation (maximum file size, number of records, maximum number of concurrent users, etc.)
  4. Behavior in response to problems in the programming environment (system crash, unavailable network, full hard-disk, printer not ready)
  5. Protection against unauthorized access to data and programs

Posted in Labels: | 0 comments

Web Testing- Functional System Testing

Posted On at 6:44 PM by Rajeev Prabhakaran

System tests check that the software functions properly from end-to-end. The components of the system include: A database, Web-enable application software modules, Web servers, Web-enabled application frameworks deploy Web browser software, TCP/IP networking routers, media servers to stream audio and video, and messaging services for email. A common mistake of test professionals is to believe that they are conducting system tests while they are actually testing a single component of the system. For example, checking that the Web server returns a page is not a system test if the page contains only a static HTML page

Posted in Labels: | 0 comments

Web Testing- HTML Content Testing and Validation

Posted On at 6:40 PM by Rajeev Prabhakaran

HTML content checking tests makes a request to a Web page, parses the response for HTTP hyperlinks, requests hyperlinks from their associated host, and if the links returned successful or exceptional conditions. The downside is that the hyperlinks in a Web-enabled application are dynamic and can change, depending on the user's actions. There is little way to know the context of the hyperlinks in a Web-enabled application. Just checking the links' validity is meaningless if not misleading. These tests were meant to test static Web sites, not Web-enabled application

Posted in Labels: | 0 comments
Subscribe to: Posts (Atom)