Mozilla Add-On: ReloadEvery

ReloadEvery:

This Mozilla Add-On helps me reload page when I am not in-front of system.

In Testing it helps me Reload the page so that Server don't log me out of the application. You can easy set the time when page should reload like 5s, 10s, 1m, 10m etc. It can be enabled for single tab or all the tabs.

Click here to download latest version and for more information on ReloadEvery.

Mozilla Add-On: FireShort - Webpage Screenshots

FireShort:

1. Its Mozilla Add-On which help us in taking screenshot of your webpage.
2. You can also edit the screenshot.
3. Upload to Facebook, Picasa etc.
4. You can integrate it with IE and Chrome browser.

Click here to download latest version and for more information on Fireshot.

TestiPhone.com - iPhone Simulator

This is a web browser based simulator for quickly testing your iPhone web applications. This tool has been so far tested and working using Internet Explorer 7, FireFox 2 and Safari 3.

http://www.testiphone.com/

How to get logs in Android device???

aLogcat:

aLogcat is Android app which allows you to collect the log from device. This can be very helpful for developer to debug the app. Many times we see that it’s hard to reproduce crashes in the application. To capture that you can always use aLogcat.

You can view the log in plain text or HTML. No USB required.

Set log format / level / buffer, filter logs by regex, clear log file, save to SD.

Share logs via any application that handles plain text or HTML sharing, including Gmail, Email, Bluetooth, and others.

Optionally save log files at specified intervals in the background.

You can download the app from following link.

http://code.google.com/p/alogcat/

This app is also available in Android Market and AppBrain.

How did you learn Testing???

I read text book about testing.

I read blogs.

Watch videos about testing.

I ask people to share their thought about testing.

Do you really think by doing all this you will learn how to test?

My answer will be big NO.

Until unless we practice what we read, what we listen, what people do........... We will never learn testing. Best thing to learn is spreading the knowledge whatever you learn.

Please share your thoughts.

Always report nonreproducible bugs!! They may be time bombs.

Non reproducible bugs can be most expensive bugs, company might release.......

We observe many of the time program miss behavior in way you can't replicate it. You see failure but don't know how to reproduce it. 

You are always in dilemma whether to report or not. What will customer think? credibility ?? etc etc....

Programmer have tool that you don't have. If you report symptoms clearly it will be easy to trace bug. And bug getting fixed.

Yes, we know that nonproducible bugs are ignored by programmer. But its always good to have them in bug tacker.

When you report a nonproducible bug, make it very clear that you cannot replicate the bug. Some tracking system have the field for this----Can you reproduce this: Yes/no/intermittent/unknown.

Using PrintScreen, a screen recording etc can help you prove the existence of UFO

Please share your views.

How to take screenshot in Android Nexus S device

Now, it is possible to get live feed and take screenshot on Nexus S device.

Connect USB connector to Phone and computer.

Enable USB-Debugging on your cell phone. This option is hidden in Settings -> Application -> Development.

Download 91 PC Suite for Android


http://91.pandaapp.com/pcsuite/

Install the application.

Right click on phone symbol in System Tray, mouse hover on 3^rd option and select English. (It is Chinese app hence default language will be Chinese).

After sometime it will prompt to Install Driver.

Can manually downloaded Samsung USB driver from http://www.mediafire.com/?dmuyy2dlgzv

Complete the installation.

Click on “Media” tab.

Click on “Full-Screen ScreenSnap”.

We can see live feed in system monitor.

Press Prt Scr key to take screenshot.

Note:

1.    Use only Nexus USB connector.

2.    Every time you open the application it will open in default language Chinese. Hence always need to change language from System Tray.

3.    Always Mobile should be connected to computer though USB to take screenshot.

Please let me know if you have any query/suggestion(s). Also let me know if you have any better or easy solution.

Web Validator Tools

1. Markup Validator:

http://validator.w3.org/

2. CSS Validator:

http://jigsaw.w3.org/css-validator/

3. FEED Validator:

http://feedvalidator.org/

4. Link Checker:

http://validator.w3.org/checklink/

5. Accessibility Tool:

http://www.contentquality.com/

6. W3C mobileOK Checker:

http://validator.w3.org/mobile/

Default path of iPhone/iPad/iPod Crash Reports

Mac OS X:

~/Library/Logs/CrashReporter/MobileDevice/<DEVICE_NAME>

Windows XP:

C:\Documents and Settings\<USERNAME>\Application Data\Apple Computer\Logs\CrashReporter\MobileDevice\<DEVICE_NAME>

Windows Vista:

C:\Users\<USERNAME>\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\<DEVICE_NAME>

Windows 7:

C:\Users\<USERNAME>\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\<DEVICE_NAME>

General scenario to test desktop application manually

General scenario to be covered to test desktop application manually:

1. Functionality test as per specs of the application

2. Usability tests.

3. Screen load/ Operation times/ Response times.

4. Fail over scenarios, mostly depend on application

5. Compatibility testing.

6. Installation, then re-installation testing.

7. Recovery testing, what if application crashes. Is data lost?

8. Print functionality.

9. Keyboard shortcuts (Hot-keys).

10. Cut/ Copy/ Paste functionality.

11. Minimize/ Maximize/ Resize.

12. Help functionality.

White box and black box testing

White box and black box testing are terms used to describe the point of view a test engineer takes when designing test cases. Black box being an external view of the test object and white box being an internal view. Software testing is partly intuitive, but largely systematic. Good testing involves much more than just running the program a few times to see whether it works. Thorough analysis of the program under test, backed by a broad knowledge of testing techniques and tools are prerequisites to systematic testing. Software Testing is the process of executing software in a controlled manner; in order to answer the question “Does this software behave as specified?” Software testing is used in association with Verification and Validation. Verification is the checking of or testing of items, including software, for conformance and consistency with an associated specification. Software testing is just one kind of verification, which also uses techniques as reviews, inspections, walk-through. Validation is the process of checking what has been specified is what the user actually wanted.

Software Testing

It is the process used to help identify the correctness, completeness, security, and quality of developed computer software. Testing is a process of technical investigation, performed on behalf of stakeholders, that is intended to reveal quality-related information about the product with respect to the context in which it is intended to operate. This includes, but is not limited to, the process of executing a program or application with the intent of finding errors. Quality is not an absolute; it is value to some person. With that in mind, testing can never completely establish the correctness of arbitrary computer software; testing furnishes a criticism or comparison that compares the state and behavior of the product against a specification. An important point is that software testing should be distinguished from the separate discipline of Software Quality Assurance (SQA), which encompasses all business process areas, not just testing.