Tuesday, August 18, 2009

H1N1 Influenza A: Symptoms & Precautions

Although I am deviating from scope of my Blog , but I believe since my blog is read by many of my freinds I wish to share Some info regarding H1N1.

Measures to consider, particularly when you are in an area where flu is rampant in the community:
Maintain good personal hygiene. Wash your hands frequently. Carry a hand sanitizer for use when soap and water aren't readily available
Avoid touching your face.
Avoid people who seem to be sick.
Avoid crowds as much as possible.
If you cannot avoid crowds, consider wearing a face mask or a respirator (if you are trained in using a respirator).
Monitor your health, and seek medical attention if you feel unwell.
To reduce the spread of flu:
Cover coughs and sneezes with a mask or a tissue.
Stay at home if you are unwell.
Limit your contact with others as much as possible.
Contact the Doctor or the Nodal Center nearest to your location, if you or your children develop flu-like symptoms.
When you arrive at the hospital, ensure that you tell them that you have recently been in an area that has reported H1N1 influenza.
The symptoms of H1N1 swine flu in people are similar to the symptoms of regular human flu and include fever, cough, sore throat, body aches, headache, chills and fatigue. Some people have reported diarrhoea and vomiting associated with H1N1 swine flu. Severe illness (pneumonia and respiratory failure) and even deaths have been reported with H1N1 swine flu infection. Like seasonal flu, H1N1 swine flu may cause a worsening of underlying chronic diseases.In adults, emergency warning signs that need urgent medical attention include:
Difficulty in breathing or shortness of breath
Pain or pressure in the chest or abdomen
Sudden dizziness
Confusion
Severe or persistent vomiting
Flu-like symptoms improve but then return with fever and worse cough
You can refer these links for more Information :
Govt of India - Ministry of Health website on H1N1 guidelines and information
WHO website on H1N1 Infleunza
Centers for Disease Control and Prevention website
National Institute of Virology website
if you are visiting an infected area use N95 Masks.These are 3 tier masks that are much better than 1 tier masks that are avilable @ a cheaper rate in the Market.

Saturday, August 1, 2009

How to Check Website on Multiple Browsers


As a website tester you have the ability to create a bug free website. Unfortunately, you do not have the ability to control which internet browsers will be using to view your site. Because each browser behaves differently you will need to test your projects on multiple browsers.

In most of cases the variation from one browser to another will be minor, and probably will not even be noticeable to the most of visitor. However, sometimes your site will be crash or have major problems in a particular browser. The best way to be sure that your site is usable in different browsers is sufficient testing.

Is there any way to Test Your Website in Different Browsers?

You should be familiar with which browsers are most commonly used by your visitors. After all, you’ll want to make those browsers the biggest priority.

Once you have to know which browsers are most commonly used by visitors after that you should focus your efforts on those browsers. You can easily install several different browsers like Internet Explorer, Mozilla Firefox, Safari and Netscape, but there are huge amount of browsers available you will never be able to install them all. So you will need the help of specific tools.

BrowserShots – Test your website in different browsers. BrowserShots creates screenshots of your pages in a wide variety of browsers and displays them for testing. It also has several additional options.

What is the difference between Priority and Severity?

The terms Priority and Severity are used in Bug Tracking to share the importance of a bug among the team and to fix it.

Severity
1. The Severity status is used to explain how badly the deviation is affecting the build.
2. The severity type is defined by the tester based on the written test cases and functionality.

Ex : If an application or a web page crashes when a remote link is clicked, in this case clicking the remote link by an user is rare but the impact of application crashing is severe, so the severity is high and priority is low.

Priority
1. The Priority status is set by the tester to the developer mentioning the time frame to fix a defect. If High priority is mentioned then the developer has to fix it at the earliest.
2. The priority status is set based on the customer requirements.

Ex : If the company name is misspelled in the home page of a website, then the priority is high and the severity is low to fix it.


Application Testing

Testing Considerations for GUI


Application: C, C++

Testing : Memory leak detection, Code coverage, Static and
dynamic testing, Test coverage analysis, Runtime
error detection, Automated component testing,
Measurement of maintainability, Portability,
Complexity, Standards compliance, Boundary
testing conditions.

Application: Java Applications/Applets.

Testing : Automated component testing, Functional testing
Performance testing, Applets/application testing,
Code coverage, Boundary conditions testing.


Application: Win 32-based Applications

Testing : Memory leak detection of win32 programs,
Performance testing, Stress testing of windows
Applications and system clients.
Testing Considerations for GUI

Communication; aspects to be tested are:

  • Tool tips and status bar

Missing information

  • Enable/ Disable toolbar buttons
  • Wrong/ misleading/ confusing information
  • Help text and Error messages
  • Training documents

Dialog Boxes; aspects to be tested are:

  • Keyboard actions
  • Mouse actions
  • Canceling
  • Okaying
  • Default buttons
  • Layout error
  • Modal
  • Window buttons
  • Sizable
  • Title/ Icon
  • Tab order
  • Display layout
  • Boundary conditions
  • Sorting
  • Active window
  • Memory leak

Command structure; aspects to be tested are:

  • Menus
  • Popup menus
  • Command Line Parameters
  • State transitions

Program rigidity; aspects to be tested are:

  • User options
  • Control
  • Output

Preferences; aspects to be tested are:

  • User tailor-ability
  • Visual preferences
  • Localization

Usability; aspects to be tested are:

  • Accessibility
  • Responsiveness
  • Efficiency
  • Comprehensibility
  • User scenarios
  • Ease of use

Localization; aspects to be tested are:

  • Translation
  • English-only dependencies
  • Cultural dependencies
  • Unicode
  • Currency
  • Date/ Time
  • Constants
  • Dialog contingency