THE BASICS OF STORING TEST DATA in Font

Draw PDF-417 2d barcode in Font THE BASICS OF STORING TEST DATA

Listing 3-10. Writing Test Results to a Microsoft Access Database VB .NET 'Make sure to add Imports System.Data.OleDb at the top of the code page Dim cn As New OleDbConnection _ ("Provider=Microsoft.jet.oledb.4.0;Data Source=TestResultsDB.mdb") Dim iRet As Integer cn.Open() Dim cmd As New OleDbCommand( _ "Insert into TestResults (TestID, TestDate, Reqmt, Tester, Result) " & _ "Values (3, '01-Jan-2006', 'Test Reqmt ABC', 'M. Sweeney', 1)", cn) iRet = cmd.ExecuteNonQuery cn.Close() C# //Make sure to add using System.Data.OleDb at the top of the code page OleDbConnection cn = new OleDbConnection( "Provider=Microsoft.jet.oledb.4.0;Data Source=TestResultsDB.mdb"); int iRet; cn.Open(); OleDbCommand cmd = new OleDbCommand( "Insert into TestResults (TestID, TestDate, Reqmt, Tester, Result) " + "Values (3, '01-Jan-2006', 'Test Reqmt ABC', 'M. Sweeney', 1)", cn); iRet = cmd.ExecuteNonQuery(); cn.Close(); Let s examine this code. The first line imports or uses the System.Data.OleDb namespace. This OleDb namespace contains code for ODBC database access, and the System.Data.SQLClient namespace contains resources for accessing Microsoft s SQL Server database. Since you want to use Microsoft Access, you must use the general library, which is located in the System.Data.OleDb namespace. The next line creates a Connection object and points it to the TestResultsDB.mdb database. (The TestResultsDB database is a sample Access database that we ve created for this book and have included in the code for this chapter. You will use it in Exercise 3-3.) In this example, the database resides in the bin folder of the application; otherwise, you could need a full pathname to the database location. After the integer variable declaration, the following command actually opens the connection: cn.Open();

Once the database is opened successfully, the next few lines of Listing 3-10, repeated here, comprise a single statement that will create a Command object and set it up so that when the Command object is executed, it will send a SQL Insert statement to the TestResults table within the database: VB .NET Dim cmd As New OleDbCommand( _ "Insert into TestResults (TestID, TestDate, Reqmt, Tester, Result) " & _ "Values (3, '01-Jan-2006', 'Test Reqmt ABC', 'M. Sweeney', 1)", cn) C# OleDbCommand cmd = new OleDbCommand( "Insert into TestResults (TestID, TestDate, Reqmt, Tester, Result) " + "Values (3, '01-Jan-2006', 'Test Reqmt ABC', 'M. Sweeney', 1)", cn); Finally, in the last line of Listing 3-10, repeated here, the ExecuteNonQuery() method of the Command object is called to actually execute the command against the database: VB .NET iRet = cmd.ExecuteNonQuery C# iRet = cmd.ExecuteNonQuery; Now that you know the basics of creating and using the Connection and Command objects, you re ready to start exploring how to incorporate database access into your automated tests.

The SQL Insert statement used in Listing 3-10 inserts into a specially created table called TestResults. The TestResults table in the TestResultsDB database has a number of fields useful for reporting test information. You can modify this table within Microsoft Access, to add or remove columns, as desired (note that you will need to have Microsoft Access installed to make changes). Table 3-2 lists the fields in the TestResults table with explanations for their intended use.

Table 3-2. Fields in the TestResults Table (TestResultsDB Sample Database)

A unique number so that every test result can be identified individually. Date this entry is added. Requirements identifier so this test result can be traced back to test requirements. Name of the tester running the test that entered this record.

Table 3-2. Fields in the TestResults Table (TestResultsDB Sample Database) (Continued)

This number represents the test run. Many test IDs could be linked to one TestNumber. This number represents the particular build of the software release. Pass or Fail of this test. 0 will be stored if the test fails and 1 if the test passes. Any additional comments desired for this particular test result.

Notice that in the code in Listing 3-10, our Insert statement inserts into only five columns of the table: TestID, TestDate, Reqmt, Tester, and Result. It may not be necessary to use every column every time, but you should be consistent across all tests.

Note The code in Listing 3-10 is contained in the 3 Exercise folder. This demo application is called