Tuesday, July 8, 2014

What is the difference between SDLC and STLC?

Software Development Life Cycle involves the complete Verification and Validation of a Process or a Project.

Whereas Software Testing Life Cycle involves only Validation. Analysis, Design, Software requirement specifications, Development Process (Coding and Application development), Testing Process (Preparation Of Test Plan, Preparation of Test cases, Testing, Bug reporting, Test Logs & Test Reports), Release and Maintenance.

Whereas Software Testing Life Cycle involves Preparation of Test Plan, Preparation of Test cases, Test execution, Bug reporting & Tracking, Regression Testing and Test Closure.

STLC is a Part of SDLC.
Software Development Life Cycle involves business requirement specifications.

Monday, November 18, 2013

High Severity And Low Priority and High priority -Low severity

High Severity And Low Priority :- If there is an application if that application crashes after multiple use of any functionality.
Eg. :- save Button use 150 times then that application will crash

Means High Severity because application crashed but Low Priority because no need to debug right now you can debug it after some days.

High priority -Low severity - Wrong spelling in Company logos displayed in the application.

Monday, August 12, 2013

In simple way to understand Load stress and performance Testing.

Load testing:
Load testing is a test to check the user’s response time, of number of users using any one scenario (single business process) of the same application at the same time.

Stress testing:
This type of testing the application is tested against heavy load such as complex numerical values, large number of inputs, large number of queries etc. which checks for the stress/load the applications can withstand.

Performance testing:
Performance testing is a test to check the user’s response time of number of users using multiple scenarios (multiple business process) of the same application at the same time.

Monday, August 5, 2013

Some user full test case for mobile app like: Call, GPS, Network, Orientation, sound, lock/unlock Application

GPS in background application can get or locate the location through app in background only for some time .


application in foreground can update location everytime and the symbol of GPS will be displayed every time.


if location service is off for a particular app from settings than a message should be displayed for the user to “ON” the Gps from settings.
call in foreground application will be immediately get in background as soon as call comes and if user receives the call and than run the application the design of the application should not be disturbed.

in background same applies
network
application should give proper message to the user when ever there is no network.


application should detect the network automatically as network comes.
orientiation
as per requirement of the client we should check the orientation of application.


UI should be clear in both the orientation.
audio file in background when user is playing an audio file and make the app in background than file sound should get stop. And when again user have to play the file when come back in foreground.
application in background application should be get stopped it activity or any service hit in background.
sound activity if device in silent mode when device is in silent mode than the application sound should not be heared.
lock and unlock device
if user lock the device and than unlock than check the behaviour of the application .

What is Push Notifications?

Push Notifications are messages that are sent to users who have opted in to receive them.
Notification’ means providing information.

Activity Test Cases:
Notification in foreground when notification comes in foreground than the notificaton will display directly on app.

background when notification comes and device is locked , if user open the device with sliding the notification than the application should get launch.


when notification comes and device is not locked than the notification comes in banner if user click on the banner than the application launch and if user is unable to click on banner than the notification with showed in the notification tray. From the notification tray user can click on the notification and user can move to the application.


when notification and user didn't click on banner than the notification count should get updated on the icon of the application.

Thursday, August 1, 2013

What is the advantage of Symbian OS devices comparing with J2me and Brew OS devices?

  • - Symbian is the latest OS where as j2me and Brew OSs are old ones.
  • - Symbian OS has SIS file format where as j2me has JAR file format which means this is a third party software and anybody can develop softwares in this OS.
  • - Symbian is a fast browsing and a fast operating system. j2me is not as fast.
  • - Symbian OS provide touchscreen phones such as UIQ phones. No such facility on j2me.
  • - Symbain OS has superior hardware access to the phone compared to j2me and Brew OS
  • - Symbian OS offers rich UI.

Difference between Smoke & Sanity Software Testing

Smoke Testing: Software Testing done to ensure that whether the build can be accepted for through software testing or not. Basically, it is done to check the stability of the build received for software testing.

Sanity testing: After receiving a build with minor changes in the code or functionality, a subset of regression test cases are executed that to check whether it rectified the software bugs or issues and no other software bug is introduced by the changes. Sometimes, when multiple cycles of regression testing are executed, sanity testing of the software can be done at later cycles after through regression test cycles. If we are moving a build from staging / testing server to production server, sanity testing of the software application can be done to check that whether the build is sane enough to move to further at production server or not.

Difference between Smoke & Sanity Software Testing:
  • Smoke testing is a wide approach where all areas of the software application are tested without getting into too deep. However, a sanity software testing is a narrow regression testing with a focus on one or a small set of areas of functionality of the software application.
  • The test cases for smoke testing of the software can be either manual or automated. However, a sanity test is generally without test scripts or test cases.
  • Smoke testing is done to ensure whether the main functions of the software application are working or not. During smoke testing of the software, we do not go into finer details. However, sanity testing is a cursory software testing type. It is done whenever a quick round of software testing can prove that the software application is functioning according to business / functional requirements.
  • Smoke testing of the software application is done to check whether the build can be accepted for through software testing. Sanity testing of the software is to ensure whether the requirements are met or not.

Thursday, October 18, 2012

Functional and Non Functional Testing

Functional Testing: Testing the application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.
Functional Testing covers:
·      Unit Testing
·      Smoke testing / Sanity testing
·      Integration Testing (Top Down, Bottom up Testing)
·      Interface & Usability Testing
·      System Testing
·      Regression Testing
·      Pre User Acceptance Testing(Alpha & Beta)
·      User Acceptance Testing
·      White Box & Black Box Testing
·      Globalization & Localization Testing
Non-Functional Testing: Testing the application against client's and performance requirement. Non-Functioning testing is done based on the requirements and test scenarios defined by the client.
Non-Functional Testing covers:
·      Load and Performance Testing
·      Ergonomics Testing
·      Stress & Volume Testing
·      Compatibility & Migration Testing
·      Data Conversion Testing
·      Security / Penetration Testing
·      Operational Readiness Testing
·      Installation Testing
·      Security Testing (Application Security, Network Security, System Security)



Saturday, July 7, 2012

How to create test plan in Jmeter ?



1. Download the binary

You can get the binary here.

2. Unzip the tarball/zip file

I extracted it file to 
/Users/theo/tools/jakarta-jmeter-2.3.1
3. Start up JMeter- It seem like to (Double click on Jmeter.bat files)

 Create a Test Plan:

4. Create a Thread Group:

Thread Group:
Thread Group is the beginning point of any Test Plan. Thread Group is set of request that simulate the user actions and all the elements of Test Plan should be under Thread Group. It works like LoadRunner Scenario. In Thread Group we define the Number of User, Ramp Up, and Loop Count.
  • Number of Thread (User), as a name we define the number of users, who will simulate the performance test steps.
  • Ramp-Up option used to set the time that waited between each and every user run. Suppose if you have define 5 then each and every user will activate after 5 seconds. All the time will be in seconds.
  • Loop Count is the option where we set that how many times users will repeat the actions.

5. Add a Sampler: With the help of sampler JMeter send the request to web server.
A sampler is a type of request you want to make. In this example, I used an HTTP request to test load to a web server. It’s good to note JMeter supports multiple types of samplers including web services, JMS, and JDBC. Add a sampler by selecting the Thread Group you just created, right-click, select Add -> Sampler -> HTTP Request.
Configurable properties include:
  • Server Name – what the ip or url is to the server the request it to
  • Port – the port the server is listening to
  • Protocol – the protocol (http, https, etc)
  • Method – HTTP method (POST,GET, PUT, DELETE, etc)
  • Path – the URL path to request
6. Add a Listener:
 Listener is same as Result window of any tools. It will help to analyze the test result. JMeter provides different kind of Listener which we used according to our needs.
See JMeter is having lots of element of Test Plan but these are enough to create sample script for Web Application. For the more details about Test Plan element refer this link.

7. Run the test!


Tuesday, July 3, 2012

JMeter Interview Questions and Answers


Q1 . Does Jmeter generate any scripts? How to use the Jmeter tool and also the How to analyze the results?

A1.When you create a test in Jmeter, save the file. The file saves with the extension .jmx.
Open the .jmx file in an editor. There you can see script.
Q2. For what purpose are Junit and Jmeter used?

A2.Jmeter is a Performance Tool. It is used to test the performance of the application. Apache JMeter is a 100% pure Java desktop application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.

What is Jmeter?
Jmeter is one of the Java tools which is used to perform load testing client/server applications.
Apache JMeter is open source software, a 100% pure Java desktop application
designed to load test functional behavior and measure performance of the application.
It was originally designed for testing Web Applications but has since expanded to other test functions

what are the other applications tested by Jmeter? 
JMeter may be used to test performance both on static and dynamic resources (files, Servlets, Perl scripts, Java Objects, Data Bases and Queries, FTP Servers and more)

What do u see when u open a jmeter?
By default,
Test Plan
Workbench
can be seen

What is Test Plan in Jmeter?
Test plan describes a series of steps JMeter will execute when run.
A complete test plan will consist of one or more Thread Groups, logic controllers, sample generating controllers, listeners, timers, assertions, and configuration elements.

What is Work bench?
The Workbench is simply an area to store test elements while you are in the process of constructing a test.  
The Workbench is a sandbox for any test or portion of a test that you are working on.
When you are ready to test what you have designed in the Workbench, you can copy or move the elements into the Test Plan.

It also contains Non- Test Elements
Http mirror sever
Http Proxy server
which is not available in the thread group & Test plan 


What is Thread Group?
Thread group elements are the beginning points of any test plan.

  1. All controllers and samplers must be under a thread group. 
  2. Listeners may be placed directly under the test plan, in which case they will apply to all the thread groups. 
  3. The controls for a thread group allow you to:
  • Set the number of threads
  • Set the ramp-up period
  • Set the number of times to execute the test 
What are the parts of thread group?

  • Sampler :Sends various types of requests to the server
  • Listeners : Results of the Run can be viewed & saved
  • Timer : Makes the run more realistic by inserting delays between the requests
  • Controller: responsible for controlling the flow of the thread group. If we have defined request to be executed on some logic like if-then-else or loop structure in java
  • Config Element: Info about the requests are added to work with samplers using this.
  • Assertion: To check if the responses are within given time and containing expected data
What are Controllers and its types? 
JMeter has two types of Controllers

Samplers Controllers 
Logical Controllers 

Samplers Controllers 
Samplers tell JMeter to send requests to a server.
For example, add an HTTP Request Sampler if you want JMeter to send an HTTP request. You can also customize a request by adding one or more Configuration Elements to a Sampler.

Logical Controllers 

Logical Controllers let you customize the logic that JMeter uses to decide when to send requests.
Logic Controllers can change the order of requests coming from their child elements.
For example, you can add an Interleave Logic Controller to alternate between two HTTP Request Samplers.

What is Configuration element?

A configuration element works closely with a Sampler
Configuration elements can be used to set up defaults and variables for later use by samplers.
Note that these elements are processed at the start of the scope in which they are found, i.e. before any samplers in the same scope.

Its elements:

CSV Data Set Config: Used to read lines from a file, and split them into variables.
HTTP Authorization Manager: You can specify one or more user logins for web pages that are restricted using server authentication
Java Request Defaults: You can set default values for Java testing
HTTP Cookie Manager: The Cookie Manager element has two functions:  
  1. It stores and sends cookies just like a web browser.
  2. Second, you can manually add a cookie to the Cookie Manager. However, if you do this, the cookie will be shared by all JMeter threads

HTTP Request Defaults: This element lets you set default values that your HTTP Request controllers use.
HTTP Header Manager: The Header Manager lets you add or override HTTP request headers




What are Listeners?
A listener is a component that shows the results of the samples
the results can be shown in a tree, tables, graphs or simply written to a log file

The Graph Results listener plots the response times on a graph.
The "View Results Tree" Listener shows details of sampler requests and responses, and can display basic HTML and XML representations of the response.
Other listeners provide summary or aggregation information.

Every listener in JMeter provides a field to indicate the file to store data to.
They also provide means to view, save, and read saved test results.

Q. How do you ensure re-usability  in your JMeter scripts?
A.
 · Using config elements like "CSV Data Set Config", "User Defined Variables", etc for greater data reuse
·    Modularizing shared tasks and invoking them via a "Module Controller".
·  Writing your own BeanShell functions, and reusing them.
Does Jmeter generate any scripts? How to use the Jmeter tool and also the How to analyze the results?
When you create a test in Jmeter, save the file. The file saves with the extension .jmx.
Open the .jmx file in an editor. There you can see script.

For what purpose Jmeter used?
Jmeter is a Performance Tool. It is used to test the performance of the application. Apache JMeter is a 100% pure Java desktop application designed to load test functional behavior and measure performance. It was originally designed for testing Web Applications but has since expanded to other test functions.

Can we Parametrize via Jmeter?
Yes, you can parametrize via CSV file, User define variables or XML sheet.



Reference Site----

http://java-success.blogspot.in/2011/10/jmeter-interview-questions-and-answers.html