General terms in Testing

General terms are used in the Testing with in a Development Department :

New : The Status used When a new bug is reported to the Development team..

Open: When we report a bug to the Development team we mark the status of Bug as open.

Re-open :The Status used This bug was once resolved, but the resolution was not done correctly. The bug found again.

Pass : The Status used If the portion of software is working correctly, I.e no bugs are present there.

Fail : The Status used If The Defect is present. And produce some unexpected result.

Closed : The Status used if we find the defect is fixed.

Not an issue : The Status used If the Tester Report the defect is not produced there .

Deferred : The Status used If the Developer think he has no time to fix the defect and this defect will not effect to any other portion of the application.

What to test?

Content Checking

The website has to be tested for accuracy, completeness, consistency, spelling and accessibility (Stout, 2001). These areas are the first things judged by the user. Users must have the best possible experience with your website. Even just a faulty image can create a bad impression on the user and may not visit your site again.

 Browser Compatibility :-----

There are a number of different browsers and browser options. A website has to be designed to be compatible for a majority of the browsers. This still leaves room for creativity. Even with Microsoftís Internet Explorer and Netscapeís Navigator this is an issue because of the different versions people are or still are using (Gerrard, 2000b).

 Transaction Testing

This is very critical in an e-business application. The software a website is utilizing has to be forced to invoke its various components and whether the direct and indirect interfaces work correctly. The information entered by the user should make it to the database in the proper ways. When the user calls for information contained in the database, the proper data must be returned.

Usability :

Designers should always remember that the experience of the user in their website must be as pleasant as possible. How the user interacts with the website is very important. There may be cases when the user is someone very familiar with website browsing but not necessarily a testing expert.

Web site Testing

How important is it to test your website before going live? Site testing is essential so that every aspect of your website is functioning, especially software. Site testing ensures that there are no broken links, no missing graphics, no misspelled words, no bugs in the software, and that download time is as specified. There are many software out there that do the site testing for you. I will tackle only a few here that were recommended by experts. This will give an insight on how the software works and how extensive the

testing is.

STLC phases

Software Testing Life Cycle:-

According to ISTQB the STLC follows these phases........

planning & control --- Test planning is the activity of verifying the mission of testing, defining the objectives of testing and the specification of test activities in order to meet the objectives and mission.
Test control is the ongoing activity of comparing actual progress against the plan, and reporting the status, including deviations from the plan. It involves taking actions necessary to meet the mission and objectives of the project.
analysis & design --- Test analysis and design is the activity where general testing objectives are transformed into tangible test conditions and test cases.
implementation & execution --- Test implementation and execution is the activity where test procedures or scripts are specified by combining the test cases in a particular order and including any other information needed for test execution, the environment is set up and the tests are run.
evaluating exit criteria and reporting --- Evaluating exit criteria is the activity where test execution is assessed against the defined objectives. This should be done for each test level.
test closure activities ---Test closure activities collect data from completed test activities to consolidate experience, testware, facts and numbers.

Testing of a particular product follows many rules.