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.)

 

A beta testing invitation from "feedspot".

Hello Friends,

I am adding a small info OR you can say a recent news related to beta testing invitation.

As an software test engineer A.K.A QA :)

This what I like most, checking/learning and breaking/enjoying new things either doing it by myself OR other like mined people offer, beta testing or reviewing invitations to me.  

On 25th Aug. I got a another Beta Testing, review offer from a SaaS based feed service known as "FeedSpot".

http://www.feedspot.com/

Adding a screen-shot of the mail :) 

Note: Before this one, I recently execute beta testing on Uhuru App-Cloud and many others in the past.

The reason is not branding yourself but sharing an idea, if I can do it, you can too, remove the 'im' from impossible and make it possible :) 

So, happy QA/test hunting.

QTP Script Use Run And Results - Kapil Sharma

QTP CheckPoints-1

Training Session: H.P-QTP 11.0: Class 2.1. (Working-Part 1) - Kapil Sharma

Training Session: H.P-QTP 11.0: Class 2.1. (Working-Part 1)

Now, our trial QTP 11.0 application test tool installed on Win-7 PC based on Oracle Virtual Box.

It's time to start this test tool and see what we can do with this tool. 

I will create separate blog labels and YouTube training clips for each function's for this test automation tool. 

So, let us start the QTP-11.0. 

Training Session: H.P-QTP 11.0: Class 1.2 (Installation-Part2) - Kapil Sharma

Training Session: H.P-QTP 11.0: Class 1.2 (Installation-Part2)

1.) Click QuickTest Professional Setup to start the QuickTest Professional Setup program.  

     This will install the QTP 11.0 application tool on user window PC. 

2.) These are some screen-shots during installation, user will observed during installation. 

Training Session: H.P-QTP 11.0: Class 1.1 (Installation-Part1)

H.P-QTP 11.0: Class 1.1 (Installation-Par1)

Prerequisites:
1.) Win-7 OS (http://windows.microsoft.com/en-us/windows7/get-know-windows-7)
2.) Oracle Virtual Box (https://www.virtualbox.org/)
3.) QTP 11.0 Trail Version
     (http://www8.hp.com/us/en/software-solutions/software.html?compURI=1172957#)

Steps for downloading QTP 11.0 trial version : 
1. From Trials and Demos > HP QTP Essentials 11.0 English Valuation. (Web GUI testing only)
2. Fill out the form, if required.
3. Select download option for QTP trial version.

Quick Test Professional 11 Introduction: 
http://merc-training.cce.hp.com/online/ITByArt-SAMPLES/QTP01IT-110%20SAMPLE/QuickTest_Pro_Sample/website/xml/content/a9157633c/index.xml

Test cases design techniques:

These are the following test case design techniques. 

A.) Boundary Value Analysis. (BVA)

B.) Error Guessing.

C.) Equivalence Class Partition. (ECP)  

D.) Cause-Effect Graph Analysis. (CEG)

Cyclometric complexity of a software:

It's a metric to measure the software (logic) complexity. 

Formula:--> E-N+2, where 'E' is no.of edges and 'N' is number of nodes.

Test Strategy:

Test Strategy:   

Test strategy is basically implementation of test levels (Test actions) in a test environments. 

The main aim of test strategy to plan test levels a.k.a test actions in a planned condition or conditions, where AUT (Application under test) is present. 

And test approach is super-set of test strategy. 

So, the inner core of test strategy is test levels than the strategy and in end the test approach used by the test expert to apply the strategy. 

Test implementators can also used ISO 9126 template for strategy. 

Boundary Value Analysis:

Boundary Value Analysis:

To understand this, let us a simple example:

Suppose in Las Vegas based casino a slot machine software require BVA testing.

Now, to test according to BVA, we need to make three groups of data. 

Group-1:  | Group-2:  | Group-3:
-0, -1,-2   |  0,1,2       | 10,11,12

Now, out of three groups, the Group-2 is valid, if user got 0,1,2 numbers in slot display, he/she may win some prizes. 

So to check the software working fine, we need to create three set of data. 
If Group 1, or 3 got passed the user got prize information in displaying the machine, than the software is buggy. If no information regarding prize shows up than the software passed.

Scrot_Linux_ScreenShot_Utility:

Scrot_Linux_ScreenShot_Utility:

To use scrot, one must have scrot installed, in vanilla linux shell, this feature is not present.

A/B or A:B Testing. - Kapil Sharma

A/B or A:B Testing:

A/B or A:B is a testing method to compare web pages, to gather UI feedback before making the site live for global audience, mostly done on web sites. 

For example, if you are an tester and you asked to run the A:B tests on client web site.  

The best way to run it by sharing the site with two different set of audience, one with original site contents and other set with some enhanced or different mutated UI version site. 

And check which site experiences are comfortable and user friendly for two different target audience.    

Benefits: 
1.) Page Permanence.
2.) UI feedback.
3.) Test ideas without impacting the live site.

Second session of exploratory testing.

Second session of exploratory testing:

Today, I am checking the Google released API. And stumble upon this main link.

https://developers.google.com/drive/training/drive-apps/getting-started/ 

https://developers.google.com/drive/apps-overview >> Leads to 404 error. 

Uhuru Application cloud service: Pre-Beta Testing. - Kapil Sharma

UhuruAppCloud Service: (Exploration Testing)

It's a new cloud based application hosting service. 

Nice and fast UI, I can say that, I tried my self.  May be my net speed is high :P

It's not a Beta or release service, they are just testing, so errors may observe to users.  

I came cross-one related to server. Looking to get error logs to find out what happens...... that's the fun part of testing :) 

Every time something new to learn and explore :)   

Going to report more to nice uhuru team to find the culprit. Let start digging more guys this is really a great chance of exploration testing, try in your weekdays or weekend if you want to learn with fun :) 

Testing opportunity on Ubuntu devices. - Kapil Sharma

Testing opportunity on Ubuntu devices:

If you want to make your testing career more towards R &D and flyer to learn new more Linux.

This is the right opportunity for you. I will shortly update all basics and start-up steps in this direction. 

Source: 
http://www.ubuntu.com/devices/phone/app-ecosystem