October 30, 2009

Bug of the Month

   'Known Software Bug' Disrupts Brain-Tumor Zapping: The maker of a life-saving radiation therapy device has patched a software bug that could cause the system's emergency stop button to fail to stop, following an incident at a Cleveland hospital in which medical staff had to physically pull a patient from the maw of the machine. (Thanks to Wired)

Source:- http://www.wired.com/threatlevel/2009/10/gamma/

October 28, 2009

How and Why to Clear Your Cache?

Often referred to as the cache, the Temporary Internet Files folder contains a kind of travel record of the items you have seen, heard, or downloaded from the Web, including images, sounds, Web pages, even cookies. Typically these items are stored in the Temporary Internet Files folder.

Storing these files in your cache can make browsing the Web faster because it usually takes your computer less time to display a Web page when it can call up some of the page's elements or even the entire page from your local Temporary Internet Files folder.

You can adjust your Internet Explorer 6 settings to automatically clear the cache whenever you close Internet Explorer 6. Go to the Tools menu, and click Internet Options. Click the Advanced tab. In the "Settings" box, scroll down to the section labeled "Security," and click to check the box next to the "Empty Temporary Internet Files folder when browser is closed" option. Click OK to finish. This option does not delete cookies, but it will clear your cache of other files when you close your browser.

If you tend to go online a lot and have ample space on your computer, you might want to increase the size of your Temporary Internet Files folder. Why? Because Internet Explorer 6 will read already-viewed files from the cache first rather than take the time to download the same page from the Web, thus saving you time and money.On the General tab, in the Temporary Internet Files section, click the Settings button. This will open the Settings box.In the Settings box, under Amount of disk space to use, you can slide the bar to the right to increase the amount of disk space used by your Temporary Internet Files folder.

While it's true that the more files you can load from your hard disk, the faster your browsing speed, it's also true that those pages on the Web might have changed since being stored on your computer. You might not want to miss fresh content just to save a little time. Fortunately, in addition to the size of the cache, you can also customize how often Internet Explorer 6 checks the Web for updated content.In the Settings box, there are four ways to check for newer versions of pages that are stored in the Temporary Internet Files folder:
•Every visit to the page: You're assured of the most current content, but it's slower to browse previously viewed pages.
•Every time you start Internet Explorer 6: On your first visit to a page, Internet Explorer 6 will check for new information, but not on subsequent visits in the same browsing session.
•Automatically: Internet Explorer 6 will check automatically for any new content.
•Never: This option is fastest, but you could be viewing old content from the cache. To refresh the page, press the F5 button on your keyboard—this will connect you to the page on the Web and download new information to the Temporary Internet files folder.

objective questions with answer

(1) Which of the following is not one of the techniques to find defects
a) Operational Techniques
b) Functional Techniques
c) Dynamic Techniques
d) Static Techniques

Ans: a

(2) Quality Assurance methods are usually considered
a) Detective
b) Corrective
c) Preventive
d) Proactive

Ans: c

(3) Who has the primary responsibility of setting the quality culture in the organization?
a) Senior Management
b) The Training Dept
c) The Quality Dept
d) Nobody

Ans: c

October 27, 2009

What is a GUI Prototype?

   A GUI (Graphical User Interface) prototype is nothing but an initial design built during the Design Phase. It may be a small program consisting of just the main screens (functions are not implemented only how it would appear is done, "Back", "Next" , "Submit" etc buttons may work for navigation purpose only). After the client approval of the screens (the GUI) they are finalized. Then starts the actual coding phase. Prototype may be in different language or using some tools. It is developed for fast understanding of application.

October 16, 2009

Is accessibility testing different from GUI testing ?


Accessibility testing is different from GUI testing.

GUI testing: Test for Graphical user interface. How site looks? Test for site design in all browsers, design should not corrupts.

Accessibility testing: Test for how site is usable for partial or complete disabled persons. For example: if a user has eye problem, weak sight. Then is there any hearing feature for  words displayed on site.

I think now difference is crystal clear. Any question, please comment.

October 14, 2009

Difference between test case and test scenario

Test case is a condition which is executed for expected output with predefined set of steps with known inputs. Generally a test case have

1) Precondition
2) Steps to execute
3) Input data
4) Expected output
5) Status (Pass/Fail)

Test Scenario is set of test cases. What it means, If you have to withdraw money from an ATM machine, then it is a scenario. But to withdraw money, you need to execute many test cases, needs to provide many inputs and you get many outputs and finally your money with receipt of transaction.

Any query, please comment.

October 13, 2009

How to log a defect?

How to log a defect?

I have used 4 defect/bug tracking tools which are:

1) Microsoft VSTS
2) Bugzilla
3) Mantis
4) Redmine

AS per my experience, what I found common and most valuable thing in bug reporting are:

1) Defect title
2) Defect Summary
3) Defect description ( Steps to reproduce)
4) Severity
5) Screenshot if any.

October 12, 2009

Test cases for Lift


Lift are always as per requiremnts. So, It will not better to start with test cases without requirements.

Here I am taking the simplest example of metro rail lift used to get from Ticket floor (TF) to Platform floor (PF). Requirement is passanger should able to use lift to go and come back from Ticket floor to platform floor. Precondition is passanger is on TF.

1) When light is on for the lift and no request has been made to go from TF to PF, button light should Off.
2) When passanger made request for PF, button light should ON.
3) When button light is ON and if lift is available at TF, the door should open.
4) When button light is ON and if lift is not available at TF, the indicator light should indicate the movement of lift from PF to TF.
5) When door opens, it should made a sound.
6) When passanger is in the lift, if passanger press the hold button lift door should not close.
7) If pasanger press the lift close button, it should close immediately otherwise should close automatically after fixed time.
8) If lift fan is ON, and passanger press FAN button it should get OFF or vice versa.
9) Try to call using CALL button to help persons using lift.
10) Now test for overload, if lift is for 10 persons or  100KG weight, try for 11 or 12 persons to use the lift at one time.
11) Lift door should not open when lift is moving, even after pressing lift opening button.
12) Try to use Pass button of the lift to overcome an request.
13) Let lift is at PF, it should not move to TF if no request made at TF and vice versa.
14) Let passanger get in lift from TF anf starts moving to PF, then if other request made to PF, then lift should complete first request first and come back to TF after PF.
15) If electricity get gone, Lift should not make a major jerks and starts working on emergency backup.

Friends, there can be above 100 test cases depending on requirement. I just write the major test cases for simplest lift requirement. Please comment if any query.

How to interact with the developer about the bug?

How to interact with a developer about the bug is really a gud question that can be asked to any candidate in an interview. Why because, we all as tester reports bug to developers but how many of them get fixed by developers depends on our bug reporting. this is like a stranger ask you about a way and how better we can explain it to that stranger, so that he/she needs not to ask about it to somebody else.

Bug reprting is also like an art. When we say for example login is not working, what developer will fix, he don't know where is the problem? and he will not intrested to see full module code because he can fix the fix the issue by just fixing a function. May be e-mail id is not compared and validated well with DB, and that's why login is not working. So a tester needs to tell and try to define the exact issue in bug report.

Tester should not force the developer to fix an issue, but he should explain the bug in such a way that developer thought it important to fix it.

For any query, please comment.

Search Here...

Popular Posts

Quick Test Professional