Asking the right question

Testing is all about learning, how can you learn without asking question? But asking so many questions, specially irrelevant one's are really dangerous ;) But avoiding asking questions is a sin for a tester. Start asking question relevant or irrelevant, as time will goes by and you will become more and more experience you will know what to ask and when to ask. Believe me you will get better and better each and everyday. So, if you are not practicing it, start today. Have courage, face and learn. Best of luck :)

Running Selenium Webdriver 2.0 in Opera

Following are the steps I used to run selenium webdriver in Opera
(Windows, Mozilla Firefox, Opera, Eclipse, Java)

Selenium IDE with Mozilla Firefox
- Open your Mozilla Firefox browser and Selenium IDE add on
- Record a simple and short test case for your testing application through Firefox and IDE
- Replay it ensure that cases runs alright as you recorded
- Export Test Case as JUnit4(Webdriver) Script from IDE

Selenium Webdriver/ Selenium 2.0
- Run Eclipse
- Create an new project
- Create a Class for the project without Main()
- Add the downloaded webdriver .jar files to your project in Java Build path-> Library
- Download and add another additional jar for Opera, selenium-server-standalone-2.18.0.jar
- Paste the JUnit4 code exported from IDE
- Hit the play button and enjoy ;)

Opera Configaration
- Opera latest versions
- Replace the code in exported JUnit code
-" driver = new FirefoxDriver(); " replace it with " driver = new OperaDriver(); "
- import com.opera.core.systems.OperaDriver;

Running Selenium Webdriver 2.0 in IE

Following are the steps I used to run selenium webdriver in IE
(Windows, Mozilla Firefox, IE, Eclipse, Java)

Selenium IDE with Mozilla Firefox
- Open your Mozilla Firefox browser and Selenium IDE add on
- Record a simple and short test case for your testing application through Firefox and IDE
- Replay it ensure that cases runs alright as you recorded
- Export Test Case as JUnit4(Webdriver) Script from IDE

Selenium Webdriver/ Selenium 2.0
- Run Eclipse
- Create an new project
- Create a Class for the project without Main()
- Add the downloaded webdriver .jar files to your project in Java Build path-> Library
- Paste the JUnit4 code exported from IDE
- Hit the play button and enjoy ;)

IE Configaration
- IE 6 or Higher versions
- Go to IE Settings -> Internet options -> Security tab -> Enable protected mode for all type of connections
- Replace the code in exported JUnit code
-" driver = new FirefoxDriver(); " replace it with " driver = new InternetExplorerDriver(); "
- import org.openqa.selenium.ie.InternetExplorerDriver;

Running test scripts in Selenium 2.0

Following are the steps I used to run selenium webdriver
(Windows, Mozilla Firefox, Eclipse, Java)

Selenium IDE
- Open your Mozilla Firefox browser and Selenium IDE add on
- Record a simple and short test case for your testing application through Firefox and IDE
- Replay it ensure that cases runs alright as you recorded
- Export Test Case as JUnit4(Webdriver) Script from IDE

Selenium Webdriver/ Selenium 2.0
- Run Eclipse
- Create an new project
- Create a Class for the project without Main()
- Add the downloaded webdriver .jar files to your project in Java Build path-> Library
- Paste the JUnit4 code exported from IDE
- Hit the play button and enjoy ;)

Selenium cont.

I am listing my steps I used to configure selenium in my windows machine, in two different parts

Selenium IDE
- Add it to your Mozilla Firefox browser

Selenium Webdriver
- Download and install Java Runtime Enviroment
- Download and install Frame work you gonna use, I am using Eclipse Classic
- Download all the listed .jar files for webdriver

Move to my next post to running automation in webdriver :)

Lets start automation

So many automation application is available today but 3 most popular is Selenium, Watir and Sahi. Lets start with Selenium as it is most popular, have a very strong community for support and many many tutorial is available over the web to start. Selenium many different parts for different type of functionality. I am gonna use Selenium IDE, Selenium RC and Selenium Webdriver or Selenium 2.0 and others I am ignoring at the moment.

Selenium IDE
- An add on for Mozilla Firefox
- Used for recording activity in browser in terms of web applications
- Can export automation script of variety range of programming language to use in RC/ Webdriver/ Selenium 2.0

Selenium RC/ Selenium Webdriver / Selenium 2.0 (Java)
- Selenim RC or Webdriver or 2.0 is actually is the same application
- RC is the older version with have limited functionality and Webdriver/ Selenium 2.0 is the latest with more functionality in terms of automation scripting
- Support programming languages, I am focusing only in Java
- Exported script of IDE can be Import here

So, lets roll on my next post ;)

So, where your mind is?

- Do not test when you don't want to
- Do not test when you don't understand the domain
- Do not test when your mind is fighting with your personal problems
- Do not test in extreme time limit pressure
- Do not test one day to fill up other days work time
- Do not test when you are not prepare for test
.
.
.
Well if you have to then make sure you test that part again and don't forget to keep your mind in testing not somewhere else :D Remember you are compromising with quality, heavy to bare ;)

Testing tools!

Working with tools is a must for software tester professionals. As much used to you got with your tools that much you got good in your work. But it impose dependency in your test, so you are actually believing a or many software to test another software. Is this good? As we know believing is a sin for testers. But did you notice how much you believing on software in to day to day daily life? This argument can goes many pages long, so I am cutting it down to my opinion. According to me doesn't matter how much you disbelieve, in some point you have to rely on your tools. Its not possible to be fully independent to test.

But avoid software which provide results for you, use tools for inspection but don't rely on their result. Result should be made by you the tester. And mention your disbelieves in the report. OK if it is too much unprofessional to mention in report for you than take notes on those and keep it in a very handy place for you, to guide you on future. Last but not the least don't ignore this impact of believe or disbelieve, its too expensive to ignore.

Do test cases really drive you to defects?

Testing an application have many required tasks, like writing test plan, design test scenarios, writing test cases and many many more. And when you are testing based on those checklists what are you getting? Defects? Really, how many? May be they are covering application's requirement but do they cover application's functionality? To be honest this path never helped me much, I never find a worthy defect after all of these works. But surprisingly when ever I am testing any application my insight lead me to defects. And to be a lot more honest whenever I am testing, I put myself in an user seat or customer's seat very rare.

According to me Exploratory testing is the best practice for software testing, you always come up with good defects and you need to educate yourself to know that it is a defect. So, my advice would be to listen to your instincts and recognize defects at first look. That would help a lot more than any test suits.

Exit criteria

So did you determine your exit criteria for working project?

If you did then what is the base? Time, Budget or Context?

Something did you forgot? What about Maintenance testing?

So you are not assigned for it? Not in the Requirement? Not your job?

Think, think reasonably, think once again. From my experience the finest bug's came from customers, after deployment. Bugs which are really tough to think of, very much functional and realistic. Bugs which are delicious for Programmers to fix. Those bugs can build a very strong reputation in your carrier. But those visions came from experience. Experience with a good eye, reasonable mindset and with a lots of notice points. Remember if you are not noting down something very interesting facts of your application then 70% chance is there that you will do the same miss again. So, very careful about your exit criteria may be its out of spec but it is in spec for your knowledge. To grow your knowledge, and it will be big plus in that context application.

P.S
- Keep an eye on your tested software, know its behavior and cause of unexpected
- Must must must note it down, or may be it will lost in your complex brain