Sunday, 8 January 2017

How to Connect Jmeter JDBC Connection with Oracle OCI Driver

1.Open Jmeter Instance

2,Create New JDBC Recording

3.Save it as JDBC.jmx

4.In Test Plan add below jar, you can find in Oracle 11g client which is installed n your Machine.
ojdbc5.jar
ojdbc5_g.jar
ojdbc5dms.jar
ojdbc5dms_g.jar
ojdbc6.jar
ojdbc6_g.jar
ojdbc6dms.jar
ojdbc6dms_g.jar

simplefan.jar

5.Database URL =jdbc:oracle:oci:@jdbcconnection

6.JDBC Driver Class=oracle.jdbc.driver.OracleDriver

7.Username=xxxxx

8.Password=xxxxx

9.Add Script like "Select * from dual"
10.Run the Jmeter Script.
11,.Find the Result.
Thanks~

If you have any question,Please reply back to me.



How to Connect JDBC with Oracle RAC for Failover Testing.

Hi Guys,

Please follow below Steps to connect JDBC with Oracle.

1.Install Oracle 11g CLient in your Machine.
2.Create JDBC Program in Eclipse
3.in JDBC Program mention below thng in code
                 user = xxx
password = xxxxx
database = xxxxx    //TNSnames.ora file 

           URL("jdbc:oracle:oci:@" + database);
4.Go to XXXXX\product\11.2.0\client_2\network\admin\tnsnames.ora

database=
    (DESCRIPTION =  (ADDRESS = (PROTOCOL = TCP)(HOST = xxxxx)(PORT = 1521))
           (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = xxxxx)))

5.InEclipse Add Jar
     xxxxx\product\11.2.0\client_2\jdbc\lib
6.Set Class Path
7.Run your Program.
8.Go to Oracle Server
9.Down Any Node
10.The traffic should move to another Node.


Thanks~
If you have any concern,Please revert back to me.

Tuesday, 27 November 2012

Difference between various Specifications Documents – For Test Design, Test Cases & Test Procedures


Difference between various Specifications Documents – For Test Design, Test Cases & Test ProceduresIEEE 829 standard prescribes many specifications related documents. Three such documents are

1) Test Design Specifications
2) Test Case Specifications
3) Test Procedure Specifications

Let us go a bit deeper into the salient features of each of these documents being crucially important in any testing effort.
1) Test Design Specifications:

The objective of compiling test design specifications is to identify set of features or a combination of features to be tested and to identify the group of test cases that will adequately test those features. In addition to these it contains all types of refinements done to the approach described in the test plan.

The test design specification consists of following essential parts:
1) Test design specification identifier: A unique identifier is to be allocated so that the test design specification document can be distinguished from all other documents.2) Features to be tested: It describes the test items and the features that are the object of this test design specification.3) Approach refinements: It describes the test techniques to be adopted for this test design.4) Test identification: It describes a comprehensive list of test cases associated with this test design. It provides a unique identifier and a short description for every test case.
5) Acceptance criteria: It describes the criteria to confirm as to whether each feature has passed or failed during testing.
2) Test Case Specifications:The objective of compiling the test case specifications is to specify in detail each test case listed in the test design specification.

The test case specification consists of following essential parts:
1) Test case specification identifier: A unique identifier so that this document can be distinguished from all other documents.2) Test items: Identifies the items and features to be tested by the particular test case.3) Input specifications: It describes details of each & every input required by the particular test case.4) Output specifications: It describes each output expected after executing the particular test case.5) Environmental needs: It describes any special hardware, software, facilities, etc. required for the execution of the particular test case that were not listed in its associated test design specification.6) Special procedural requirements: It describes any special setup, execution, or cleanup procedures unique to the particular test case.7) Inter-case dependencies: It describes a comprehensive list of all test cases that must be executed prior to the particular test case.
3) Test Procedure Specifications:
The objective of compiling the test procedure specification is to specify the steps for executing a test case and the process for determining whether the software passed or failed the test.
The test procedure specification consists of following essential parts:
1) Test procedure specification identifier: A unique identifier is to be allocated so that the test procedure specification document can be distinguished from all other documents.
2) Objective:
It describes the objective of the test procedure and its corresponding test cases.3) Special requirements: It describes a comprehensive list of all special requirements for the execution of the particular test procedure.4) Procedure steps: It describes a comprehensive list of all steps of the procedure.

Possible steps may consist of the following:

# Set up
# Start
# Proceed
# Measure
# Shut Down
# Restart
# Stop & finally
# Wind up

Wednesday, 20 April 2011

Paisa Live.com

Earn upto Rs. 9,000 pm with PaisaLive.com!

Hi ,
I have something interesting for you - you can easily earn regular income online via PaisaLive.com!
It’s really amazing! You get paid to open & read the contents of PaisaLive mails. You also receive special discount coupons, promotions and free passes to various events in your city.
Join now and get Rs. 99 instantly, just for joining. What more, as a special bonus you get paid for inviting your friends also!
Create your PaisaLive Account & refer your friends to earn launch referral bonus on every new registration.
http://www.PaisaLive.com/register.asp?2899809-3408949
PaisaLive - Get Paid to read emails
 Earn upto Rs. 9,000 pm checking Emails. Join now!

Monday, 18 April 2011

How to search manual testing google?







                                                                                                                             ForTesting Help

ISTQB DUMP