Prepare for your Next Interview
|
Welcome to the Geeks Talk forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
This is a discussion on backend testing within the Test Director forums, part of the Software Testing category; How do we do backend testing.Whatelse do we need to know apart from basic SQL.Do we write SQL statements in the test cases, if so where do we write in ...
|
|||||||
|
|||
|
backend testing
How do we do backend testing.Whatelse do we need to know apart from basic SQL.Do we write SQL statements in the test cases, if so where do we write in TD or QC.Do we use CREATE and UPDATE statements for backend testing.I need this for my interview.
|
| Sponsored Links |
|
|||
|
Re: backend testing
hello all,
I am intersted in software testing and working as a traniee |
| The Following User Says Thank You to bhupender For This Useful Post: | ||
|
|||
|
Hi Bhupender,
Welcome to the World of Testing - Database Specific ![]() Well testing dB Migration would generally not be covered as part of a Tester's scope. There is a seperate team that looks into Migration projects.... But still if Insistent..... We could write Automated Scripts which would Compare Table Structure of both the Databases once Migrationis complete. A simple workaround would be to Describe both the table structures in the DB's and take the output to Excel Sheets. We could parameterize DB.Table Name to achieve easier use. Once the column names are in Excel, a simple Macro program to compare Range of values specified in both columns would suggest if the table was migrated successfully or not. NOTE : But even then verifying Datatype of columns would not be possible. Also checking Data Integrity would not be a part of the scope as well.. Cheers.......
__________________
Regards, V.Umesh Krishnan QA Consultant |
|
|||
|
Re: backend testing
Hi Ayodhya,
In QC we can do backend testing in SiteAdmin.We use SQL statements for customization.We write queries in Tables.we have different tables for different modules in QC.For eg fects module will have Tables like BUG,BUG TOKENS.Each table will have number of columns like BG_BUG_ID which is an integer type.When we want to change the defect id then we go for SiteAdmin BUG table and will write Query "update sequences set SQ_SEQ_VALUE='1' where SQ_SEQ_NAME='BUG' ".This query results in changing the existed defect id in defects module starts with one...then the next defect ID will be two....and so on. If you have any doubts then can get back to me any time as iam working as QC Admin...hope this information is useful for you. Thanks Deepika.P |
| The Following User Says Thank You to deepika.padakandla For This Useful Post: | ||
|
|||
|
Re: backend testing
hi dear
we do testing with nunit... http://weblogs.sqlteam.com/mladenp/a...2/15/4165.aspx Go with the flow & have fun! Else fight the flow Thanks and regards PRATAP M |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Jmeter for load testing and stress testing | dhamodharan2006 | LoadRunner | 1 | 10-06-2008 04:10 AM |
| View code that Informatica creates in backend | JobHelper | Data Warehousing | 4 | 06-06-2008 04:18 AM |
| Frontend and Backend testing | JobHelper | Testing Issues | 1 | 12-17-2006 09:55 AM |