Selenium: Class 1004 - Kapil Sharma

Selenium: Class 1004 (Selenium-WebDriver A.K.A Selenium 2.0)

This variant of selenium is more robust test automation suit for web browser automation QA. 

Selenium WebDriver comes to life by fusing two open-source projects:
1.) Selenium.
2.) Web-Driver.

 URL: http://docs.seleniumhq.org/docs/03_webdriver.jsp

To start knowing more please go thorugh the above mentioned url. After you have some basic idea regarding this automation suit. I will show you in next class how to download and use this framework using Eclipse IDE and we start writing some tests :) 

So, gear up in upcoming days, we all writing selenium web driver automation tests in Java and C#. 

Selenium: Class 1003 - Kapil Sharma

In this class we learn how to use Selenium IDE.

I shared the very basic test steps how to record user actions on this tool. 

Follow the 1-6 steps in-printed on the screen-shot, so that any one easily use this test automation tool. 

Selenium: Class 1002 - Kapil Sharma

Now, we have installed 'Selenium-IDE' on firefox browser. 

To open up this tool, we first click on the 'Tools' and than click ont he Selenium-IDE. 

Or

The installed Selenium-IDE tool icon also start showing up in the top right-hand corner of the browser tool bar.

When user opens the Selenium IDE tool, having menu options named as following:

File, Edit, Actions, Options, Help. And the tool name and its version showing up in the top title bar. 

Selenium: Class 1001 - Kapil Sharma

What is Selenium?
It's a open source test automation tool, used by many IT-MNC through out the globe for auto-QA.

From where to get it or download from?
Go to the shared site. And select 'Selenium IDE'. Make sure you are using Firefox Mozilla internet browser.
http://docs.seleniumhq.org/download/

Which version we should download?
Latest stable release is version 2.5.0, release on 01/01/2014

Where to proceed after installing the Selenium IDE tool. 
Start with the documentation section and read some basic information about this tool.

Step-By-Step: Screen-shots: 

How do QA write test cases in IT companies? - Kapil Sharma

How do QA write test cases in IT companies? 

As a test person or QA you may encounter this job task sooner or later in your glittering test career :)

All glitter is not always gold ;) But do QA cares about the gold? Naaa.....

What he/she got in return is a heavy push to do QA fast in less time rather than gain some thing for the whole QA process. This is irony of QA field :(

Anyway, it look I am deviating from my blog title.....may be this was long weekend movie side effects ;)

So, how do we create test cases in general in any IT company, do we generally follow or allow to follow a proper test plans or any use case documents. 

In general this is not a hard core QA practice. I am confirm that after this comment I am going to get a hard commenting for those who actually follow the all QA driven processes. I wish all QA have the same fate like them, to make QA life more interesting and thrilling.

So, here is how a TC creation process, I am trying to show in most general, don't take my view as all IT QA view, its just an simple individual opinion. Open mind view point required to go through this theory :P

In real a QA get some technical documents, which are most of time way ahead to his/her understanding and also his so called T.L or T.M grey matter range ;P, and these QA souls need to build a secure and bug free, gaussian test castle around the product, so that every stakeholders feel good a bout the product :D

A simple .xls sheet a word document and few more technical code snippets and more tech. jargons........

And now the TC writing process started, there is one thing is fixed and very clear and each team member know about it, its named as 'dead-line' to finished the TC............

disclaimer notice: Open to re-use and plagiarism :) 


       

Test Plan Template: - Kapil Sharma

Test Plan Template (IEEE):

Hi viewers,

If you are looking for basic structure, how to create a simple but robust test plan, you can check the shared internet site links for better understanding about Test Plans. 
The basic test plan standard provided by the IEEE (Institute of Electrical and Electronics Engineers)-829. 

Test Plan Template Links: 

1) http://en.wikipedia.org/wiki/IEEE_829

2) http://www.computing.dcu.ie/~davids/courses/CA267/ieee829mtp.pdf

3) http://standards.ieee.org/findstds/standard/829-2008.html

4) http://ranger.uta.edu/~odell/Senior_Design_Common_Materials/ANSI-IEEE%20Std%20P829-2007.pdf

Basic Testing: - Kapil Sharma

Basic Testing Process: 

1.) Smoke Testing.
2.) Sanity Testing.
3.) Regression Testing.
4.) Full Testing.

These are some basic testing phases, which are part of test activities in a software development company.

 But before above these process, one need a test plan to learn and execute the testing process.

A 'Test Plan' consists of these factors: ACCR

A.) A:--> Attribute
B.) C:--> Component  
C.) C:--> Capability  
D.) R:--> Risk

Note: 
A test plan should not consists of 'Gold-plating'. (It's a Project Management term which alert/stop software development team to do more than what asked in the scope of SLA document.)