QC Testing Process

Below is a high level view of the QC Testing Process




QC Plan and Test Strategy: Documents a high level view of the goals, scope, test environment, high level test data, test preparation, roles and responsibilities, etc.

Final QC Report: reports the number of defects found, the QC process ratings, the development actual hours, the QC actual hours, customer feedback and the defects broken down by causal codes.


Regards,

Pavankumar Nandagiri........

Wishing you & your family a Very Happy & Prosperous 2008!!!

With Love

PavanKumar Nandagiri..........

What is Bug/Defect?

Bug is a difference between the actual & expected results

Expected result -> way that the application should behave ( i.e based on the Customer requirements) when some action/event is performed on it

It's before the execution

Actual result -> The results displayed after some actions performed on the application

It's after the execution

If the expected & Actual results doesn't matches then it is called as a Bug

I,e difference between what the application is intended to do before & after the execution

Effects of Bug:

Bugs can have a wide variety of effects, with varying levels of inconvenience to the user of the program.

Some bugs have only a subtle effect on the program's functionality, and may thus lie undetected for a long time.More serious bugs may cause the program to crash or freeze leading to a denial of service

Others qualify as security bugs and might for example enable a malicious user to bypass access controls in order to obtain unauthorized privileges.

Regards,
Pavankumar Nandagiri.......

What is Risk & it's Categories

"Risk are future uncertain events with a probability of occurrence and a potential for loss”

Risk identification and management are the main concerns in every software project. Effective analysis of software risks will help to effective planning and assignments of work.

Categories of risks:

Schedule Risk:Project schedule get slip when project tasks and schedule release risks are not addressed properly.

Schedule risks mainly affect on project and finally on company economy and may lead to project failure.

Schedules often slip due to following reasons:
1. Wrong time estimation
2. Resources are not tracked properly. All resources like staff, systems, skills of individuals etc.
3. Failure to identify complex functionalities and time required to develop those functionalities.
4. Unexpected project scope expansions.

Budget Risk:

1. Wrong budget estimation.
2. Cost overruns
3. Project scope expansion

Operational Risks:

Risks of loss due to improper process implementation, failed system or some external events risks.Causes of Operational risks:

1. Failure to address priority conflicts
2. Failure to resolve the responsibilities
3. Insufficient resources
4. No proper subject training
5. No resource planning
6. No communication in team.

Technical risks:

Technical risks generally leads to failure of functionality and performance.
Causes of technical risks are:

1. Continuous changing requirements
2. No advanced technology available or the existing technology is in initial stages.
3. Product is complex to implement.
4. Difficult project modules integration.

Programmatic Risks:

These are the external risks beyond the operational limits. These are all uncertain risks are outside the control of the program.These external events can be:

1. Running out of fund.
2. Market development
3. Changing customer product strategy and priority
4. Government rule changes.


Regards,
Pavankumar nandagiri.........

Hi guys, I'm posting some information on Cookies......

Some Test cases for web application cookie testing:

The first obvious test case is to test if your application is writing cookies properly on disk. You can use the Cookie Tester application also if you don’t have any web application to test but you want to understand the cookie concept for testing.


Test cases:

1) As a Cookie privacy policy make sure from your design documents that no personal or sensitive data is stored in the cookie.

2) If you have no option than saving sensitive data in cookie make sure data stored in cookie is stored in encrypted format.

3) Make sure that there is no overuse of cookies on your site under test. Overuse of cookies will annoy users if browser is prompting for cookies more often and this could result in loss of site traffic and eventually loss of business.

4) Disable the cookies from your browser settings: If you are using cookies on your site, your sites major functionality will not work by disabling the cookies. Then try to access the web site under test. Navigate through the site. See if appropriate messages are displayed to user like "For smooth functioning of this site make sure that cookies are enabled on your browser". There should not be any page crash due to disabling the cookies. (Please make sure that you close all browsers, delete all previously written cookies before performing this test)

5) Accepts/Reject some cookies: The best way to check web site functionality is, not to accept all cookies. If you are writing 10 cookies in your web application then randomly accept some cookies say accept 5 and reject 5 cookies. For executing this test case you can set browser options to prompt whenever cookie is being written to disk. On this prompt window you can either accept or reject cookie. Try to access major functionality of web site. See if pages are getting crashed or data is getting corrupted.

6) Delete cookie: Allow site to write the cookies and then close all browsers and manually delete all cookies for web site under test. Access the web pages and check the behavior of the pages.

7) Corrupt the cookies: Corrupting cookie is easy. You know where cookies are stored. Manually edit the cookie in notepad and change the parameters to some vague values. Like alter the cookie content, Name of the cookie or expiry date of the cookie and see the site functionality. In some cases corrupted cookies allow to read the data inside it for any other domain. This should not happen in case of your web site cookies. Note that the cookies written by one domain say rediff.com can’t be accessed by other domain say yahoo.com unless and until the cookies are corrupted and someone trying to hack the cookie data.

8 ) Checking the deletion of cookies from your web application page: Some times cookie written by domain say rediff.com may be deleted by same domain but by different page under that domain. This is the general case if you are testing some ‘action tracking’ web portal. Action tracking or purchase tracking pixel is placed on the action web page and when any action or purchase occurs by user the cookie written on disk get deleted to avoid multiple action logging from same cookie. Check if reaching to your action or purchase page deletes the cookie properly and no more invalid actions or purchase get logged from same user.

9) Cookie Testing on Multiple browsers: This is the important case to check if your web application page is writing the cookies properly on different browsers as intended and site works properly using these cookies. You can test your web application on Major used browsers like Internet explorer (Various versions), Mozilla Firefox, Netscape, Opera etc.

10) If your web application is using cookies to maintain the logging state of any user then log in to your web application using some username and password. In many cases you can see the logged in user ID parameter directly in browser address bar. Change this parameter to different value say if previous user ID is 100 then make it 101 and press enter. The proper access message should be displayed to user and user should not be able to see other users account.

Regards,
PavanKumar Nandagiri......