<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://www.testingreflections.com">
<channel>
 <title>testingReflections.com - databases &amp; SQL</title>
 <link>http://www.testingreflections.com/taxonomy/view/or/119</link>
 <description></description>
 <language>en</language>
<item>
 <title>The ripple effects of cascade delete</title>
 <link>http://www.testingreflections.com/node/view/7326</link>
 <description>The topic of a cascade delete came up on a project the other day and I was surprised to find one of the project members wasn’t familiar with the term or the concept.  I thought I would share a short lesson and reflect on testing associated with cascade deletes.&lt;br /&gt;
&lt;br /&gt;
A cascade delete is when an on object is deleted in an application and on the backend in a relational database, the delete cascades through the associated tables in the database removing associated data.  (And hopefully both removing the appropriate information and leaving the other data.) The concept isn’t difficult to imagine although there are ripples of what takes place, what can go wrong, what could be tested, and how a failed delete can be found.</description>
<pubDate>Mon, 01 Sep 2008 12:59:44 -0500</pubDate></item>
<item>
 <title>Linguistic heuristics</title>
 <link>http://www.testingreflections.com/node/view/7113</link>
 <description>Searching. I’m currently testing a product that has a search feature. I’ve tested search functionality before but not a multilingual search engine that utilizes two different search engines based on the language selected. Nor have I previously worked with a search engine that uses stemming and stop words.&lt;br /&gt;
&lt;br /&gt;
I almost didn’t want to write about this – figured I would wait until I resolved my challenges before writing about it – but it occurred to me why? It’s not as though in software testing I haven’t learned that first understanding the complexities of a problem is an essential starting point.</description>
<pubDate>Sun, 22 Jun 2008 06:18:35 -0500</pubDate></item>
<item>
 <title>CMG Opens Its Content to the Public</title>
 <link>http://www.testingreflections.com/node/view/6572</link>
 <description>&lt;a href="http://www.cmg.org/national/about-cmg.html"&gt;The Computer Measurement Group (CMG)&lt;/a&gt; is making its conference proceedings from 1997 through 2005 available to the public. I believe that &lt;a href="http://www.cmg.org/conference/"&gt;CMG holds the best practical conference in performance analysis, capacity planning, and related areas&lt;/a&gt;. In addition to the areas listed below, I'd definitely add performance testing. Here is the official mail CMG sent:</description>
<pubDate>Tue, 12 Feb 2008 13:30:21 -0600</pubDate></item>
<item>
 <title>Reading Schemas</title>
 <link>http://www.testingreflections.com/node/view/6161</link>
 <description>Often the first request I make when starting work on a new application, is to request the database schema. I thought (somehow) that this was a fairly typical tester’s first step but recently working with other testers I came to realize this might not be the case.&lt;br /&gt;
&lt;br /&gt;
I thought I would quickly outline some of the things I learn from reading a database schema from a tester’s perspective.</description>
<pubDate>Thu, 28 Feb 2008 09:10:49 -0600</pubDate></item>
<item>
 <title>CMG 2007 Call for Paper</title>
 <link>http://www.testingreflections.com/node/view/5149</link>
 <description>This year performance (load, stress) testing will be a focus track at &lt;a href="http://www.cmg.org/conference/cmg2007/index.html"&gt;the CMG 2007 conference&lt;/a&gt;. It is the best conference, by my opinion, about performance-related topics. Below is the official text:&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.cmg.org"&gt;The Computer Measurement Group (CMG)&lt;/a&gt; &lt;a href="http://www.cmg.org/conference/cmg2007/callpap.html"&gt;calls for papers and presentations&lt;/a&gt; for &lt;a href="http://www.cmg.org/conference/cmg2007/index.html"&gt;the 33rd International Conference&lt;/a&gt; to be held in San Diego, California, December 2nd through 7th, 2007.  The 2007 CMG conference will cover &lt;b&gt;load and stress testing, benchmarking, performance optimization, software performance engineering&lt;/b&gt;, resource management, capacity analysis, simulation and analytic modeling, and cost management with special emphasis on Virtualization, System Oriented Architecture (SOA), IT Service Management and IT Infrastructure Library (ITIL), and the technology implications of globalization.</description>
<pubDate>Sun, 11 Mar 2007 10:58:19 -0500</pubDate></item>
<item>
 <title>connectionstrings.com</title>
 <link>http://www.testingreflections.com/node/view/4878</link>
 <description>&lt;a href="http://connectionstrings.com/"&gt;connectionstrings.com&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
If you didn't know about connectionstrings.com, you need to know about connectionstrings.com.  Formats for every connection string under the sun apparently...</description>
<pubDate>Tue, 23 Jan 2007 15:38:38 -0600</pubDate></item>
<item>
 <title>Using Ruby Multithreading Capabilities for Database Testing</title>
 <link>http://www.testingreflections.com/node/view/2587</link>
 <description>&lt;b&gt;Using Multithreading and ADODB in Ruby&lt;/b&gt;&lt;br /&gt;
&lt;br /&gt;
Ruby Scripting Language is emerging as a tester’s language for test automation. Ruby is a very feature reach and powerful language. We had a situation where we need to connect to different databases and fire a SELECT query at same point of time. I tried this various other alternatives, but no results.&lt;br /&gt;
&lt;br /&gt;
Then I saw multithreading support in Ruby and implemented following code using it. While doing this I wanted to access databases using ADO and I could not found help on how to use ADO in Ruby, after trial and error I got the following code working. I am sharing this code so others can use this as a reference for using ADO in Ruby.</description>
<pubDate>Wed, 20 Jul 2005 06:19:15 -0500</pubDate></item>
<item>
 <title>Toplink-in-memory: run database tests in memory</title>
 <link>http://www.testingreflections.com/node/view/2469</link>
 <description>Java library to speed up the running of automated tests for projects that use toplink to access databases. It allows you to run the application in memory, rather than against a database.</description>
<pubDate>Thu, 07 Jul 2005 15:11:14 -0500</pubDate></item>
<item>
 <title>Thycotic DatabaseScripter: database rollback tool</title>
 <link>http://www.testingreflections.com/node/view/2434</link>
 <description>Thycotic.DatabaseScripter is a simple utility that generates a stored procedure called "SETUP" which will remove all data from your database and then reinsert it in the correct order.  It uses the system tables in the database to identify foreign key dependencies and make sure data is manipulated int he appropriate manner.</description>
<pubDate>Mon, 04 Jul 2005 00:49:38 -0500</pubDate></item>
<item>
 <title>Simplify Data Layer Unit Testing using Enterprise Services</title>
 <link>http://www.testingreflections.com/node/view/2168</link>
 <description>Despite all the hype surrounding unit testing and Test Driven Development (TDD) many developers don't see them as useful processes that are applicable to the production of real-world applications. One reason is that once you get down to the intricacies of application development, all of the easy testing you've heard so much about can vanish. You may find yourself writing unit tests that are hard to implement against real code. This is often the case in database testing, where TDD can quickly lose its appeal, and force you to revert your processes to the previous real-world methodologies your team employed. Here, I'll present some techniques to make your testing process easier, even when developing real-world applications, using unit testing.</description>
<pubDate>Thu, 19 May 2005 00:38:26 -0500</pubDate></item>
<item>
 <title>Extracting Column Names for a Table in SQL as a CSV String</title>
 <link>http://www.testingreflections.com/node/view/1681</link>
 <description>&lt;p&gt;I had a need (creating CSV &lt;a href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_bcp_61et.asp"&gt;BCP&lt;/a&gt; files) that required knowing the column names of a MS SQL table in the order they were created. Some &lt;a href="http://blogs.consultantsguild.com/index.php/mclerget/2005/02/07/dynamic_sql_insert_generator_unleashed_1"&gt;inspiration&lt;/a&gt; from Mark Clerget and&amp;nbsp;a little fooling around with SQL Query Analyzer resulted in the following.&lt;/p&gt;</description>
<pubDate>Sun, 20 Feb 2005 16:22:49 -0600</pubDate></item>
<item>
 <title>Dynamic SQL INSERT Generator Unleashed!</title>
 <link>http://www.testingreflections.com/node/view/1606</link>
 <description>&lt;p&gt;Mark Clerget has another excellent post on using SQL to generate SQL. This time Mark demonstrates how to generate a series of INSERT statements from an arbitrary table.&lt;/p&gt; &lt;blockquote dir="ltr"&gt; &lt;p&gt;So you are probably saying, "Great, so you can generate a CREATE TABLE statement...Whoopee!". Well, if I could help you fill that table or tables using a script that dynamically generates INSERT statements based on the contents of a table, would that be worth something to you? Great! Read further and lets really impress those SQL jockey friends of yours. [&lt;a href="http://blogs.consultantsguild.com/index.php/mclerget/2005/02/07/dynamic_sql_insert_generator_unleashed_1"&gt;Mark Clerget's Blog&lt;/a&gt;]&lt;/p&gt;</description>
<pubDate>Wed, 09 Feb 2005 23:59:48 -0600</pubDate></item>
<item>
 <title>Keeping Databases In-Synch With Your Source Control</title>
 <link>http://www.testingreflections.com/node/view/1518</link>
 <description>&lt;p&gt;&lt;a href="http://www.consultantsguild.com/JakeLawlor.html"&gt;Jake Lawlor&lt;/a&gt; has a great &lt;a href="http://blogs.consultantsguild.com/index.php/jlawlor/2004/12/02/keeping_databases_in_synch_with_your_sou"&gt;post&lt;/a&gt; on keeping cruft out of your database. &lt;p&gt; &lt;blockquote dir="ltr"&gt; &lt;p dir="ltr"&gt;&lt;b&gt;Benefits of Approach:&lt;/b&gt; By doing this you get a versioned history of changes to your database. You also get versioned stage directories for dev, test and prod environments that have all the schema and re-runnable database objects at that point in time. These versioned stage directories correlate to a label in VSS. By automating the application of the schema and the dropping and recreating of the re-runnable objects your database will reflect your source control. &lt;/p&gt;</description>
<pubDate>Sat, 29 Jan 2005 04:30:04 -0600</pubDate></item>
<item>
 <title>Database Testing</title>
 <link>http://www.testingreflections.com/node/view/1508</link>
 <description>[textile]

Last weekend we held the first &lt;a href="http://www.iwst2005.com/"&gt;Indianapolis Workshops on Software Testing&lt;/a&gt;. The attendees were:

&lt;ul&gt;
&lt;li&gt;Mike Kelly&lt;/li&gt;
&lt;li&gt;Jason Horn&lt;/li&gt;
&lt;li&gt;Steve Lannon&lt;/li&gt;
&lt;li&gt;Denise Autry&lt;/li&gt;
&lt;li&gt;Linda Ellison&lt;/li&gt;
&lt;li&gt;Mike Goempel&lt;/li&gt;
&lt;li&gt;Rick Wellinghoff&lt;/li&gt;
&lt;/ul&gt;

Note that all attendees were from the Indianapolis area.&lt;/P&gt;

The topic we focused on for the five hour workshop was database testing. The following is a summary of presentations and ideas shared.&lt;/P&gt;</description>
<pubDate>Thu, 28 Sep 2006 19:31:25 -0500</pubDate></item>
<item>
 <title>SnapDAL: data access layer for .NET code</title>
 <link>http://www.testingreflections.com/node/view/1323</link>
 <description>SnapDAL is a data access layer (DAL) for your .net code. It is designed to make programming against databases and other sources of data easier, with less code, and higher reliability than you could do on your own without lots of discipline. SnapDAL is built with the idea of helping you write testable data access code by support Mock Objects natively as a first class development tool.</description>
<pubDate>Fri, 17 Dec 2004 00:29:54 -0600</pubDate></item>
</channel>
</rss>
