Selenium IDE Beginners Guide

Learn Selenium IDE basics in just 10 minutes 

1) Selenium IDE Introduction and it's Features

2) Selenium IDE Installation Guide

Source:
Tester Tools is our partner Blog

Server Side Testing Interview Question

A) What does Question Mark symbol (?) and hash Symbol (&) means in URL?

1)?  Separates URL and list of parameters

2) & separates each parameter

B) What are the different types of web servers?

• Apache web server - the HTTP web server
• Apache Tomcat
• Microsoft's Internet Information Services (IIS) Windows Server
• Nginx web server
• Oracle Web Tier

C) What are the different types of Hosting servers?

• Windows
• Linux

D) What is the difference between HTTP and HTTPS?

• HTTP: (Hypertext Transfer Protocol): HTTP is not secured and it operats at application layer and it does not require any certificate to access data. It uses port no 80 for communication.

•  HTTPS: (Hypertext Transfer Protocol Secure): HTTPS is secured and operates at transport layer and It requires certificates to access data. It uses port no 443 for communication

E) What are the below Servers error means?

All  (200 To 206) are Successful Status Codes
All  (300 To 307) are  Redirection Status Codes


All 4xx (400 To 499) are Client Error

400 à Bad Requests

401 à Unauthorized error

403 à Forbidden Error

404 à Not found error
409 à Conflict

All 5xx (500 To 599) are all server side errors

500 à Internal Server Error

502 à Bad Gateway

503à Services Unavailable

504à Gateway Timeout

F) How Domain Name calls server IP?

 Every Domain Name (www.xyz.com) is having its own unique Domain Name System (DNS) and in DNS we have to mention server IP which is nothing but the path of hosting server where all code and DB is present 

G) Difference between Severity and priority?

      Priority:

• High Priority: Key features does not work
• Low Priority: features that is rarely used does not work

      Severity:

• High Severity: Key features does not work
• Low Severity: In company logo company name is incorrect

H)  What is Null Pointer exception?

NullPointerException is a RuntimeException . In Java, a special null can be assigned to an object reference. NullPointerException is thrown when an application attempts to use an object reference, having the null value. 

I)  HTTP Protocol or HTTP Methods or web GET, POST, PUT, DELETE?

Ans: http://www.w3schools.com/tags/ref_httpmethods.asp

Get: 

• GET requests should never be used when dealing with sensitive data
• GET requests have length restrictions
• GET requests should be used only to retrieve data

Post:

• POST requests have no restrictions on data length
• Used to post data on server

Security	GET is less secure compared to POST because data sent is part of the URL Never use GET when sending passwords or other sensitive information!	POST is a little safer than GET because the parameters are not stored in browser  history or in web server logs
Visibility	Data is visible to everyone in the URL	Data is not displayed in the URL

Put Vs Post:

PUT is meant as a a method for "uploading" stuff to a particular URI, or overwriting what is already in that URI.

POST, on the other hand, is a way of submitting data RELATED to a given URI.

Ans:

K) Client Side and Server Side Validation?
Ans: http://net-informations.com/faq/asp/validation.htm

QA Or Test Engineer’s Pay scale

Test Engineer Pay scale

Salary of a Software Tester varies from company to company, but still there is a substantial salary gap between Developers and Testers. I would not like to comment about the scenario for any other company but as far as India is concerned this has always been the trend. Personally speaking when I started my career as a Software Tester the initial salary being offered to me was only Rs.8000 per month. Even now, though I am having 2.6 years of experience in Software Testing Industry, I have to strive hard to earn a salary as per my expectation or Industry standards.
The competition is also increasing in the field, thus yielding Recruiters with more and more option to hire from the large pool of skilled resources. While most of the Freshers look for an early start to their career while keeping the market competition in mind, they get easily convinced to work at lower pay scale.
Adding to owes is a general mindset that I have come through “If I am not a good at development then and I should get into testing”.
               Dear peoples I would like to frankly tell you one thing that if you are here in Software Testing Industry just because you were not good at development or whatever else, then you are surely not going to succeed in Software Testing Industry. It’s not a sarcasm but a bitter reality, as our Industry is changing at a rapid rate and automation is a need. So, basically you need to be having adequate knowledge of programming skills along with an bend towards adapting to new technologies. This inability to adapt and grow according to the changing market is also one of the major reason for low pay standards in Software Testing Industry.
                 In this scenario if you have got a good start to your career in Software Testing Industry then it’s only up-to you to shape your career in a fruitful way.
So it’s about my personal experience. Let us have a look at salaries being offered by different organizations to my some of my friends:
1)  Working with XXX(Pune), he is having an experience of more than 2 years.
Current Designation : QA
Current Salary : Approximately Rs. 3.6 LPA  ( Obviously he is earning more than me J)
2)    Working with XXXXX (Nagpur), he is having an experience of more than 6 years.
Current Designation : Module Lead
Current Salary : Approximately Rs. 6.25 LPA
3)     Working with XXX  Solutions(Mumbai), he is having an experience of more than 1.5 years.
Current Designation : Test Engineer
Current Salary : Approximately Rs. 3.0 LPA
4)   Working with XXX (Pune), he is having an experience of more than 1.6 years.
Current Designation : Automation Test Engineer
Current Salary : Approximately Rs. 3.5 LPA
So friends here I conclude, competition is tough but growth is in your hands, the figures above depict the same. So All The Best, stay strong….
Note: On request we are not revealing Author Identity

Software Testing Course At Nagpur

SOFTWARE TESTING-CONTENT

Contact Number:   9623332211 

Introduction

• What is software testing?
• Why is testing necessary?
• Testing principles
• Career path of Software Tester.

SDLC

• Analysis
• Design
• Coding
• Testing
• Implementation and maintenance

LEVELS OF TESTING

• Unit testing
• Integration testing
• System testing
• User acceptance test

SDLC MODELS

• Waterfall model
• Spiral model
• V-model
• Agile Testing

Verification

• Inspections
• Walk through
• Peer reviews
• Validation

Validation

• Unit Testing
• Integration Testing
• Functional testing
• System Testing
• Acceptance Testing
• Alpha Testing
• Beta Testing

Risk analysis
Testing Techniques

• White box method
  • Data coverage
  • Code coverage
• Black box method
  • Equivalence Partitioning
  • Boundary value analysis
  • Error guessing
  • Adhoc testing
  • Risk Based testing
  • Exploratory testing
• Grey box method

STLC

• Test plan
• Test case design
• Test execution
• Defect tracking

TYPES OF TESTING

• Recovery testing
• Retesting
• Regression
• Smoke Testing
• Ad-Hoc Testing
• Sanitary Testing
• Function/Non-Functional Testing
• Integration Testing

WEB TESTING

• Functionality testing
• Usability testing
• Server side interface
• Client side interface
• Performance
• Security

REVIEW

• Types of reviews
• Classes of reviews
• Difference between review and testing

Defect life cycle

• Format of defect report
• Defect lifecycle
• Meaning of different defect lifecycle status
• Severity and Priority

INTRODUCTION TO AUTOMATION TOOLS

• Introduction to automated testing
• Benifits to automated testing

QUICK TEST PROFESSIONAL

• Introduction
• Checkpoints
• Synchronization point
• Parameterization
• Reusable Actions
• Break points
• Output value

Basic of Database
Guidance for Certification [ISTQB]

PLACEMENT PREPARATION

• Resume preparation
• Technical seminar
• Project seminar
• Interview preparation
• Mock interviews
• Final test

Course Highlights
1. Experienced Faculties
2. 2.6 years of Industry Experience
Course Duration : 60 hours
Address:Opposite Of Yash bar, Old Nandanvan Plot no 94, 1st Floor above Shiv Kirana.
Contact Number:  9623332211 

Software Testing Life Cycle (STLC)

Software Testing Life Cycle (STLC)

A Software Testing Life Cycle is made up of series of phases.

1.       Requirement Gathering and Analysis

Requirements analysis is critical to the success of any project. The scope and boundary of the proposed software solution is drawn. Identifying stakeholders such as customers, end-users, system administrators etc. is the next step in requirements analysis. This is one of the most important steps in the whole process as proper identification of stakeholders enables the business analyst to draw a road map for gathering requirements. Testing Team identifies the testable requirements. Requirement can be functional or non functional. Scope of Automation (if any) is also considered.

Activities

·         Prepare Requirement Traceability Matrix (RTM).

·         Identifying the approach or setting the priorities module wise.

·         Identification of areas to be tested automatically and those requiring manual testing

Out-Put After This Phase

·         Requirement Traceability Matrix (RTM).

2.       Test Planning

A test plan is a document is created which provides detail of a systematic approach to testing. Testing Effort and Cost Estimation for the project would be calculated.

Activities

·         Project scope and expectations definition

·         Technology and methodology selection

·         Preparation of test plan document for various types of testing to be performed.

·         Testing effort estimation 

·         Definition of QA metrics

·         Resource Planning and identifying the roles and responsibility. 

·         Testing Tool Selection.

Out-Put After This Phase

·         Test Plan

·         Testing Effort Estimation

3.       Test Case Development

After Requirement is freeze followed by initial understanding, testing team starts creating Test Case or Test Scripts along with test data, which are later reviewed followed by rectifying the issues reported by reviewer. Categorization of Test Case as per their priority is also set.

Activities

·         Create test cases or Test scripts (if applicable).

·         Categorization of Test Case.

·         Create Test Data

Out-Put After This Phase

·         Test Cases/Scripts

·         Test Data

4.       Test Environment Setup

A testing environment is a setup of software and hardware on which the testing team is going to perform the testing of the software product. This setup consists of the physical setup of hardware and software setup that includes Server Operating system, client operating system, database server, front end running environment, browser (if web application) and other software components required to run this software product. These setups are done by support staff. Testing team has to ensure the conditions are met before testing is taken off. Followed by Smoke Test which verifies the Test Environment as well as stability of the build delivered to Test Team.

Activities

·         Ensure the required Hardware and Software or different combination of machines are ready

·         Perform a Smoke Test on the build delivered for Testing

Out-Put After This Phase

·         Test Machine or Test Lab

·         Smoke Test Result

5.       Test Case Execution

Test Case execution is a process of executing test cases/scripts in a logical sequence with specific test data (if available). If any Test Case/Script or Test Scenario fails, Testing Team logs the bug in Bug Tracking tool (Bugzilla, Jira, TTPro, etc.). Simultaneously a dedicated team of developers would be fixing the bugs and release the fixes in next build. Testing team shall verify the reported bug and accordingly update the Bugs logged. This cycle continues till all the bugs identified in product are fixed. Finally a Regression or Ad-hoc Testing is performed after which Test Report is prepared if all goes well.

Activities

·         Execution of Test Cases

·         Log bugs in bug tracking tool

·         Create Test Result document

·         Map defects to Test Cases in RTM

·         Verify the bug logged in new build

·         Update the bug status in bug reporting tool as per verification status

Out-Put After This Phase

·         Test Result

·         Defect Report

·         RTM with execution status

6.       Closure - Product Release

Once the test meets the exit criteria, the activities such as capturing the key outputs, lessons learned, results, logs, documents related to the project are noted down and used as a reference for future projects. Later a Causal Analysis and Resolution (CAR) Report is prepared where in best practices and cause of failures occurred are noted down.

 Activities

·         Test Metrics based on Test coverage, Cost, Time, Quality etc is prepared

·         Test Closure Report Preparation

·         Test Result Analysis is performed to calculate the defect distribution by type and severity.

·         Causal Analysis and Resolution (CAR) Report is prepared

Out-Put After This Phase

·         Test Closure Report 

·         Test Metrics

·         Causal Analysis and Resolution (CAR) Report

Note: There are different process and methodologies followed in various organizations. The above content is as per my experience in industry so far.

Please feel free to write comments if you like my post or else if your opinion is different or you may like to add any more points in them.

=====================================================================
Sponsor Ads

1) Online World Travel Guide
2) Cheap World Travelers
3) World travelers
4) World Travel Home

Bug Life Cycle Or Defect Life Cycle

Defect (Bug) Life Cycle

A Defect/Bug Life Cycle is made up of series of phases.

1. New
    When the bug is identified and logged in bug tracking tool for the first time, its state will be "NEW".
2. Open / Closed
    After a QA has posted a bug, the QA lead validates the bug. If bug is valid then he changes the state as "OPEN" and if the bug is invalid then the lead changes its state to "CLOSED".
3. Assign
    After QA lead changes the state as "OPEN", he assigns the bug to corresponding developer or developer team lead and the bug status is changed to "ASSIGN".
4. Rejected:
    If the developer feels that the bug is not valid or it has some technical limitations and cannot be fixed, he rejects the bug. He changes the state of bug to "REJECTED".
5. Duplicate:
    If the bug is logged is repeated twice or the two bugs reported has alike results and steps to reproduce, then one bug status is changed to "DUPLICATE".   
6. Deferred:
    If the development team lead decides to fix the bug in next release due to lack of time or the priority of the bug is low then he changes the state to "DEFERRED", which is later changes to "ASSIGN" when the bug is taken in consideration to be fixed.
7. InTest
    Once the developer fixes the bug, he assigns the bug to the testing team for next round of testing. Before that he changes the state of bug to "IN TEST". It specifies that the bug has been fixed and is released to testing team.
8. Verified
    Once the bug is fixed and the status is changed to "IN TEST", the tester tests the bug. If the bug is not reproducible in the software, he changes the status to "VERIFIED".
9. Reopened
    Once the bug is fixed and the status is changed to "IN TEST", the tester tests the bug. If the bug is reproducible in the software, he changes the status to "REOPENED".
10. Closed
    After the bug status is changes to "REJECTED" or "DUPLICATE" or "VERIFIED" the QA Lead verifies the comments added by the development or Testing team. When he is satisfied with the comments he changes the state to "CLOSED".

Note: There are different process and methodologies followed in various organizations. The above content is as per my experience in industry so far.

Please feel free to write comments if you like my post or else if your opinion is different or you may like to add any more points in them.

Testing /QA Interview Questions And Answers

1) Software testing:  Software testing is a methodology to find bugs in the software

2) Software Development Life Cycle( SDLC):

3) Software Testing life Cycle (STLC):  Click Her For Detail

4) Positive test case: - Test to check whether the system do what it is suppose to do.ie, checking for valid values only.

5) Negative Test Case: - Test to check whether the system will do what it is not supposed to do.ie, checking for invalid values.

6) Verification: It is a set of activity which confirms that the software is created accordance to the specification

7) Validation: Is a set of activity which confirms software is created is linked to user requirement or not

8) Retesting: Failed test case are executed to ensure that defect is really fixed

9) Regression: all passed test cases are executed on related module to verify that there is no injection of new defect to change in one of the module

10) Static: Reviewing artifacts rather than executing code

11) Dynamic: Testing Perform by executing code by giving i/p and verify o/p

12) Smoke: Is a simple test condition to ensure that the software is working properly at gross level so that further testing is done

13) Sanity: It perform to verify whether the application function according to specification or not

14) Defect: Defect indicate difference between expected and actual behavior

15) Defect Life cycle Or Bug Life Cycle: Click Here For More Details

16) White Box: It is done by developer. This require knowledge of internal structure and code of that application

17) Type of white box: 1) Statement 2) Decision3) Condition 4) path 5) loop

18) Black box: This is done by tester it mainly focus on functional requirement. By providing set of I/P and observe output.

19) Black box type: 1) BVA 2)    Equivalence class partitioning               3) state transition

 20) Alpha: It is done at developer side under controlled environment. Here developer is present

21) Beta: It is conducted at one or more customer site in live environment by end user .here developer is not present

22) Agile testing: It is testing methodology goes hand in hand to an agile software development model. Here release are quicker (within 2-3 week) and incremental are iterative in nature

23) Development Model:

1) Waterfall: It is sequential model which process through Requirement-> Design->Coding->Testing

2) Spiral: Divided into 4 phase 1) Plan2) Design3) Prototype4) test .In this model software in series of incremental realized. As we process through iteration more complete versioned is engineered product are visible. It is useful when user/developer are not cleared about the solution to developed and needs evaluator approach 

3) Agile: Here release as frequently as every week rather than month and continuous changes in requirement and welcome to be integrated

24) V-Model:
         It is extension of water fall model .here both the aspect  quality control and quality assurance are covered. Indicates that testing exits in every phase of SDLC life cycle
 

25) Test Case: test case is a set of input and output .here we pass the set of input and observe the output and system behavior

26) Test Scenario: Test scenario is a high level definition .here one can write one or more test cases

Example login

27) Test plan: Defines purpose, scope, approach, resource, responsibility of testing activities

Steps: Test Id, Intro, Scope and limitation, Test Objective, Assumption, Risk analysis, feature to be tested/Not to be, Roles and Responsibility, schedule, Test environment