Thursday, August 6, 2015

Manual Testing 1 YR Resume








(name)

                                                      Email:XXXXXXXXXXXXXX@gmail.com
                                                                                        Mobile:XXXXXXXXXXX


Career objective:

Seeking a responsible job with an opportunity for professional challenges.

Professional Experience:

Working as a Test Engineer in Krifal IT Ventures From Aug 2012. Having 11 months
Experience in Testing.


Education:

Education/Qualification
School/College
Year
Percentage/Grade
Class
B.Tech,CSE

xxxxxxxxxx
2011
63.47%
First class
Intermediate

xxxxxxxxxxxxxxxxx
2007
60.70%
First class
Secondary schooling
XXXXXXXXXXXXX
2005
81.00%
First class


Techical skills:

Testing tools : Selenium IDE, Jmeter
Bug tracking tools : Quality Center
Web technologies : HTML,CSS
Operatingsystems : Windows XP,Linux(Ubuntu) Databases : MYSQL


Expertise summary:

  • Expertise intestingwindowsbasedandWebbasedapplications
  • Expertise inperformingManual testing
  • Expertise inFunctionaltesting,Integrationtesting,Sanitytesting,Regression testing,Compatibilitytesting,Databasetesting
  •  Expertise inpreparingTest Scenarios, Test Cases andexecutingthem
Strengths:
  •  Understandingtheprioritiesandneeds of thebusinessandadaptingto thechanging requirements
  • Buildingtrust andvaluableworkingrelationshipwithteams
  •  Self-learningattitude




Project#1:

Title : MedWellRx
Role : Tester
Client :Medwell RX
Duration : Dec 2012 – Tilldate

Description:

Responsibilities:

    • Preparation of test scenarios,test cases and test data
    • Execution of test cases
    • Bug reporting




Project#2

Title : MyCabServices 
Role : Tester
Client : Krifal IT ventures
Duration : Aug2012-Dec 2012

Description: MyCabServicesis anonlineservicefor carrentals,whichisworkingin alliancewithsomeof themajorcar rentalcompaniesbycoveringallthereputedcities in India.We havea largeselectionof luxuryandeconomyclasscars, vans,andbuses for you to choose from thebestof your personal andcorporateneeds.
Responsibilities:

    • Preparation of test scenarios, test cases and test data
    • Execution of test cases
    • Bug reporting

Personal profile:

DateofBirth : 20thmay1990
Gender : Male
Nationality : Indian
Languages Known : English, Telugu and Hindi
Hobbies : Listening to music, exploring new technologies.




Declaration:

I hereby declare that the information furnished above is true to the best of my knowledge

Date:
Place: Hyderabad



(your name)

Sunday, July 26, 2015

Mouse OVer in Selenium IDE

Mouse Over Command in selenium IDE:


This command is useful for mouse over on particular element.



Mouse Over and wait command in selenium IDE:


Saturday, July 25, 2015

Software Testing Life cycle (STLC)


STLC (Software Testing Life Cycle)

Five phases are involved in STLC

1. Test initiation
2. Test Plan
3. Test design
4. Test execution
5. Test closure



1. Test initiation: Test manager will prepare test strategy for release. Strategy might be adhoc Testing, optimal Testing based on the available time for testing. If there is no sufficient time for testing usually test manager prefer adhoc test strategy. If there is sufficient time  for testing Test manager prefer Optimal test Strategy


2. Test Plan : Test lead will prepare the Test plan for the current release what are the features to be tested, what are the features not to be tested, Entry criteria, Exit criteria etc.
                                To learn more about test plan click here 
3. Test design:   In this phase testers will write the test cases based on the requirements. These requirement will vary from organisation to organisation. Requirements might be FRS(Functional Requirement specification), Use cases, wire frames(screen-shot based). Testers need to develop test cases based upon the requirements.

4. Test execution: After development is completed for the current release, application Build will be deployed to the test server for testing.
Testers will start execution of test cases on the new build.

5. Test Closure:

It is a document which consists of  following information

--> Number of test cases
--> Number of bugs/defects found while testing the application
--> Number of bugs/defects Fixed
--> Number of bugs not fixed
--> Number of bugs differed for future release

Usually test process for the release will be closed after resolving/ fixing of all major issues.



Tags: SDLC, STLC in Testing, SDLC VS STLC  STLC Phases in testing, Stlc phases in software engineering




Tuesday, July 21, 2015

Requirement Traceability matrix in softwre testing

Requirement traceability matrix(RTM) creates the mapping between requirements and testing, every requirement may have one or more test cases. with the help of  RTM we can find how many test cases we have written for the particular requirement .


Requirement

Test cases covered

Test case nos

Facebook signup

4

TC001,TC001
Facebook login
5

TC003,TC004

Facebook fogot password

6

TC005,TC006

facebook share

5

TC007
Sample RTM for facebook


Facebook login page

Sunday, June 21, 2015

Finding Xpath in different Ways

Finding Xpath in different Ways 
 
 
1.) //tagname[@attribute='value'] // to go to any class r any value
 like id r tag etc.... drictly give //tagname[@class='value']

2.) //tagname[text()='xxx'] // to go to any text directly 
give dat in xpath // tagname[text()='gotodattext'

3.) //tagname[contains(text(),'
xxx')] // to find 
any text is there r not in the linktext if spaces are there we use this

4) //tagname[@att='value']/
parent::ul // to go to immediate upper attribute we use this

5.) //tagname[@att='value']/div // to go to immediate lower attribute we use this

6) //tagname[@att='value']/
ancestor::div //to go to any of the upper
 attribute we use this by giving that attribute

7) //tagname[@att='value']/
descendant::div // to go to any lower attribute we use
 this by giving that attribute

8) //tagname[@att='value']/
following-sibling::li //to go to any
 upper attribute which are in the parent class we use this by giving that attribute 

9) //tagname[@att='value']/
preceding-sibling::li // to go to any lower 
attribute which are in the parent class we use this by giving that attribute 

//a[contains(text(),'Books')]
//div[@class='footer-menu-
wrapper']/div[1]/ul/li[1]
(//div[@class='footer-menu-
wrapper']/div)[2]/ul/li[2]

Wednesday, June 17, 2015

SELENIUM PRACTICE


Color Digest AgArAQICGQMVBBwTIRQHIwg0GUMURAZTBWQJcwV0AoEDAQ
Color Digest 2,43,2,25,

Tuesday, June 9, 2015

Database Testing In Software Testing

Database Testing :

The main aim of database testing is verify the data that are uploaded in the application (front-end) is stored in the database (back-end) or not.

In this tutorial you can learn the concepts which is required for database Testing


Pre-Requisites: MySql Need to be installed on Your System.

Click Here for the installation process of Mysql


After successful installation of mysql open mysql and create database

Creating Database in Mysql

create database <Database name>;

EX: mysql> create database Testdatabase;
Query OK, 1 row affected (0.01 sec)