Professional Documents
Culture Documents
Test-case specification in performed for system testing by keeping in mind several issues
data used for testing of DAL Builder is actual data that will be used after deployment of this
project. Which are discussed in the following subtopics
The DAL Builder software is tested at UIIT with the required hardware and software requirements.
Hardware
Processor Intel Pentium IV
RAM 512
Local Area network.
Software
OS :WinXP
Visual studio .net 2005
Microsoft SQL Server 2000
7.3 Testing Identification
A specific test should be planned for every test level to test all system components. The
test procedure should be detailed so that the system meets all user requirements.
A testing strategy is decided for testing the system so that all modules are tested to fulfill
all user requirements. A test strategy is methodology that describes the various steps that need to
be performed during testing and the time and effort required for performing them. The following
strategies are used for DAL Builder system.
Unit testing is a white-box testing techniques. The main consideration in this test is
verification of all modules of the software system. Each module is unit tested, as follows:
Unit testing the module select authentication mode: This module is used to select the
authentication mode from the available modes of authentication. User need to provide the
required input. Required input will be the user name and password in case the user selects
the SQL Server authentication, and in case the user selects the windows he will be
allowed to proceed directly. The module is test by selecting all the labs of university one
by one. The unit test results will be displayed in list view of the main form.
Unit testing the module retrieve database: This module is used to retrieve the database
whose name is provided by the user. all tables/views present in the database will be
retrieved. all fields along with all constraints i.e. unique key, foreign key etc will be
handled in this module. It needs to pick the database after successfully establishing the
connection with SQL Server.
Unit testing the module Make Settings.: This module is used to make all settings
regarding code. it is further divided into two sub groups .net settings and Stored
procedure settings. The user needs to specify all his required settings and according to
those settings the code will be generated. This module is tested by making all the settings
of code and stored procedures.
Unit testing the module Generate .NET Code: This module is used to generate the .NET
code in user specified language either it is C# or VB.NET. The generated code will
reflect all the settings as specified by the user.
Unit testing the module to generate stored procedures: this module is used to generate the
stored procedures for all the tables/views present in the database. This module is unit
tested by generating the stored procedures for all tables/views.
Integration testing is the technique for testing the interfaces of software components.
Each software components in unit tested, and all the components are integrated to perform
together. The tests are conducted to ensure that the components are working properly after
interfacing.
All modules are integrated by an incremental approach, and integration testing of the
system is performed as follows:
Integrate select authentication mode module and check that user can properly be
authenticated.
Integrate retrieve the database module and test that the software is properly retrieving the
database from the SQL server or not. And all the fields are properly retrieved and their
constraints are being handled or not.
Integrate make settings module and tested by giving all the settings of >net code and also
for all the settings of stored procedures, that all the settings are properly being activated
or not.
Integrate generate .NET code module and then tested by generating all the code for all
tables/views present in the data base.
Integrate Generate stored Procedures module and then tested by generating all the stored
procedures along with code and checked that all the stored procedures are according to
the settings of the user and fulfilling the user requirements.
7.7 System Testing
System testing involves the set of tests that ensures that the entire system performs
according to specifications.
Recovery Testing
The software system is fault tolerant. It is developed by keeping in mind all the expected
error that can effect the generation of stored procedures and code . the system will ensure that the
final product will be up to the mark and will be according to the requirement of the user. it
should reflect all the settings made by the user.
Security Testing
The system requires a logon ID and password to initiate the SQL Server . It allows only
authenticated users to log on to the system.
Stress Testing
The main function of this system is to make settings and than accordin g to that serttings
generate the code and stored procedures.. The system is tested for multiple databases and by
making different settings to ensure that the system performs accurately under all input
conditions.
Performance Testing
DAL Builder is retrieving the database than making settings and than generate code and
stored procedure according to that settings.. The performance of the software is tested at all
levels of testing. All unit modules have been tested successfully. The integration of these unit
modules also confirms that DAL Builder system is working properly under all circumstances.
Therefore, now the software fulfills all requirements of code generation for data access
layer.
7.8 Test Plan
7.8.1 Objectives
System Overview: DAL Builder will help the students and developer for coding purpose.
The user of the DAL Builder will enter the name of database and will specify required
settings for .NET as well as stored procedures .system will generate the code for data
access layer in any of the language as C# or VB.NET. And will also generate the stored
procedures. The generated code can be easily used in the user’s application. The
generated code can be decompiled into .NET assembly /DLL.
The system will help the students as well as developer in terms of easy and fast
coding,.
Document Overview: This document contains the plan and schedule for tests to be performed
on the system and the mapping of tests to specified system requirements.
Referred Documents: The referred documents are SRS and test cases developed for the
system.
Test ID
Test Name
Test Level
Test Type
Test Conditions
DAL_1
Authentication
Unit and integration testing
Input tests, output tests, verification, validation tests
Test will use existing username and password of SQL server.
DAL_2
Retrieve database.
Unit and integration testing
Input tests, output tests, verification and validation tests
Test will use all the databases existing in the SQL Server.
DAL_3
Enable Settings.
Unit and integration testing
Input tests, output tests, verification and validation tests
Test will use real-time data .
DAL_4
Enable Stored procedures settings.
Unit and integration testing
Input tests, output tests, verification and validation tests
Test will use real-time data .
DAL_5
Generate code.
Unit and integration testing
Input tests, output tests, verification and validation tests
Test will use user data, as database name etc.
DAL_6
Generate stored Procedures.
Unit and integration testing
Input tests, output tests, verification and validation tests
Test will use user data, as database name etc.
DAL_2
Retrieve database.
Anum Zar
UIIT Lab
19/05/09
DAL_3
Enable settings.
Wajeeha Islam
UIIT Lab
19/05/09
DAL_4
Enable SQL settings.
Anum Zar
UIIT Lab
19/05/09
DAL_5
Generate Code
Anum Zar
UIIT Lab
19/05/09
DAL_6
Generate Code
Wajeeha Islam
UIIT Lab
19/05/09
Test Name
Requirement Met
Authentication
When the valid inputs given to system it will log on the system main page and in case of
Invalid input it will throw an exception.
Retrieve database.
User will select the database name .if user Give invalid name he will be prompted by error
message. An exception will be generated otherwise he will be successful returned with
tables.
Retrieve tables.
System will make sure that it will retrieve all the tables/views of the database whose name
is provided by the user..
Retrieve Fields.
When user selects any table name to retrieve its fields system will simply display its fields
and will handle all constraints..
Testing Environment: HP PC (PIII), 80 GB HDD, 512 MB RAM, Visual Studio .NET 2005, and MS
SQL SERVER.
Testing Environment: HP PC (PIII), 80 GB HDD, 512 MB RAM, Visual Studio .NET 2005,
Test description: This test displays list of IP Addresses in list view. User needs to select the lab to
pick the IP Addresses from Domain Name Service (DNS).
Testing Environment: HP PC (PIII), 80 GB HDD, 512 MB RAM, Visual Studio .NET 2005,
Test description: This test displays list of IP Addresses in list view. User needs to select the lab to
pick the IP Addresses from Domain Name Service (DNS).
Testing Environment: HP PC (PIII), 80 GB HDD, 512 MB RAM, Visual Studio .NET 2005,
Testing Environment: HP PC (PIII), 80 GB HDD, 512 MB RAM, Visual Studio .NET 2005,
The objective of this test is to demonstrate that the performance of the software system
meets all requirements of DAL builder. All modules have been successfully unit tested in the
first phase. Then, the modules are incremented to perform integration testing. The performance
of the integrated system is according to DAL builder specifications. Finally, the system is fully
tested for recovery testing stress testing, and performance testing.
We try to complete the project on our level best and also try that there is minimum
deviation from the test case and the system performs according to specifications.
REPORT TYPE (1-6) Coding Issue SEVERITY (1-3) Serious ATTACHMENTS (Y/N) Yes
PROBLEM SUMMARY system checks whether SQL server is working or not after 3 minutes
PROBLEM AND HOW TO REPRODUCE IT when user want to establish the connection with SQL server
and connection is not established with SQL server after 3 minutes. there will be some problem in sql server
and SQL server should be installed.
1. Open 2.Closed
REPORT TYPE (1-6) Coding Issue SEVERITY (1-3) Minor ATTACHMENTS (Y/N) Yes
PROBLEM AND HOW TO REPRODUCE IT system will handle constraints by using a query.
COMMENTS Bug has been resolved by adding one more case of lab-1 in the case statement of IP
Addresses.
1. Open 2.Closed
REPORT TYPE (1-6) Coding Issue SEVERITY (1-3) Minor ATTACHMENTS (Y/N) Yes
PROBLEM AND HOW TO REPRODUCE IT few .net settings are not properly being reflected in final
code. this problem can be resolved by reinterpreting the code.
COMMENTS Bug has been resolved by reinterpreting the code and checking its efficiency again.
STATUS (1-2) closed
1. Open 2.Closed
REPORT TYPE (1-6) Coding Issue SEVERITY (1-3) Serious ATTACHMENTS (Y/N) Yes
PROBLEM SUMMARY when user enter the namespace. That namespace name is not being handled by the
final code generated.
CAN YOU REPRODUCE THE PROBLEM? (Y/N) Yes
PROBLEM AND HOW TO REPRODUCE. The namespace name which is generated in the code is not same
as the name entered by the user. The problem has been resolved by establishing a proper connection among
the user settings and the final code.
REPORTED BY Anum Zar DATE 19/05/2009
1. Open 2.Closed
REPORT TYPE (1-6) Coding Issue SEVERITY (1-3) Minor ATTACHMENTS (Y/N) Yes
COMMENTS Bug has been resolved by adding one more case of lab-1 in the case statement of IP
Addresses.
1. Open 2.Closed