Test Java

Today, I was browsing internet and found few useful link.

 

How to find out which version of JAVA is installed on your computer?

http://javatester.org/version.html

How do I test whether Java is working on my computer?

http://java.com/en/download/testjava.jsp

Development Environment

Development environment refers to a server tier designated to a specific stage in a release process.

Environment/Tier Name	Description
Local	Developer's desktop/workstation
Virtual Machine	VM hosted on developers desktop or possibly development server
Development	Development server aka sandbox
Integration	CI build target, or for developer testing of side effects
Test/QA	For functional, performance testing, Quality Assurance etc.
UAT	User acceptance testing
Stage/Pre-production	Mirror of production environment
Production/Live	Serves end-users/clients

Source: Wikipedia

Difference between F5 and Ctrl+F5 page refreshing

F5 gives you the same page even if the content on the site changed. This is because it may load the page from the cache.


Ctrl+F5 forces a refresh in the cache. It will ensure that if the content has changed you will be viewing the latest content of the site. 

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.

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/

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.