Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1


Ratings: (0)|Views: 128|Likes:

More info:

Published by: mysql_clustering3251 on Jul 18, 2009
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





Testing MySQL Clustering
The entire project can be divided into three primary phases -
Overview – 
The Database layer2.
The Web-Service layer3.
The Front-End GUIsOn the basis of this distribution, the overall testing plan can be categorized into twostages –1.
Scalability Testing2.
Client side GUI testing – this includes the testing of the Web Services layerThe entire process of testing was done in a virtual environment consisting of foursystems connected in a network. The virtual environment was implemented usingVirtualBox.
Test environment – 
The configuration of the host machine is as follows –
Processor – Intel® Core™ 2 Quad CPU – Q6660 @ 2.40 GHzMemory (RAM) – 4.00 GBHard-Disk – 320 GBOperating System – Windows VistaSystem Type
The configuration of the guest virtual machines are as follows –
– 32 bit Operating System1.
Processor – Intel® Core™ 2 Quad CPU – Q6660 @ 2.40 GHzMemory (RAM) – 512 MBHard-Disk – 25 GB (Dynamically expanding storage)Operating System2.
– Windows VistaProcessor – Intel® Core™ 2 Quad CPU – Q6660 @ 2.40 GHzMemory (RAM) – 256 MB
Testing MySQL Clustering
Hard-Disk – 25 GB (Dynamically expanding storage)Operating System3.
– Windows 2003Processor – Intel® Core™ 2 Quad CPU – Q6660 @ 2.40 GHzMemory (RAM) – 256 MBHard-Disk – 25 GB (Dynamically expanding storage)Operating System4.
– Fedora 10 Processor – Intel® Core™ 2 Quad CPU – Q6660 @ 2.40 GHzMemory (RAM) – 640 MBHard-Disk – 25 GB (Dynamically expanding storage)Operating System
Note – All the virtual machines use the same hard-disk and the same processor with apart of the RAM dedicated to each one of them.
– OpenSolaris 2008.11
Scalability testing is performed at the database right after the configuration of Asynchronous/Synchronous replication model.
Scalability Testing – 
Scalability testing helps in testing –
The working of the Asynchronous/Synchronous replication model.
The load that can be taken by the MySQL databases in the network.Scalability testing can be performed by running SQL scripts from the MySQL clientconsole. The SQL scripts were generated from a Java program using a randomizer (Javacode and SQL scripts included).Features of the SQL scripts –
An initial create script is provided to create the database and the tables.
Insertion of records takes places in steps, starting from 10 reaching to 10000. Atevery step the entire table is wiped out and new records are inserted. Insertion isdone using the insert scripts.
A certain portion of the records are updated. If the randomizer in the Javaprogram provides a uniform distribution, about 50% of records will be updated.Update is done using the update scripts.
Testing MySQL Clustering
A query script displays all the records present in the table – which is equal to thenumber of records inserted.
A certain portion of the records are deleted. If the randomizer in the Javaprogram provides a uniform distribution, about 50% of records will be deleted.Deletion is done using the delete scripts.
The entire contents of the table are wiped out using a delete_all script.
The database and the table can be completely removed using the purge script.
The results of scalability testing are documented at
“05 Testing - Scalability Testing” 
Observation – Asynchronous operations are comparatively faster to Synchronousoperations..The client GUI is tested considering various test scenarios. The primary test mechanismfollowed is black-box testing.
Client Side GUI Testing (Asynchronous) – 
The client side GUI is connected to the database using a web-service layer. So these testscenarios test the GUI as well as the web-service layer.The 8 operations (JDBC Insert, JDBC Update, JDBC Delete, JDBC Query, Hibernate Insert,Hibernate Update, Hibernate Delete and Hibernate Query) are tested in each of the 4GUIs (Java Swing, Java Server Faces, Java Micro Edition and ASP.net).The various test scenarios and the expected results considered are
All the record parameters are entered properly
 – the operation succeeds.Slave goes down
 – the database down indicates a backup failure. In the case of JDBC Query and Hibernate Query, all the databases show a backup failureindicating data inconsistency.Master goes down
 – the operation fails.Duplicate primary key
 – only in the case of JDBC Insert and Hibernate Insert. Theoperation fails.Required data isn’t entered properly – only in the case of JDBC Insert andHibernate Insert. Message indicating the required fields, is displayed.

Activity (4)

You've already reviewed this. Edit your review.
1 hundred reads
venkysh2u liked this
rlasmarias liked this
kunallray liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->