Hi Friends,
Can anyone explain what is exactly database testing?
Do you write different/seperate set of test cases for database testing?


There is a feature in test plan which says
"Feature to be tested and
features not to be tested"
Can anyone tell me what are those features that are to be tested
and that are not to be tested?

Naveen

The features to be tested means what the main functions to be tested .Some times Pm will these features very important to client and gives more priority.

features to be tested:say for a login window the features to be tested are
enter the valid name and valid pawssord,
features not to be tested:invalid login name and invalid pawssord,

Hi,

Hw r u Friends ? Let me is anything special.



Test Plan: Its a document detail about testing process and its approaching.

Hi
Database Testing we would be checking if the operations performed using the objects in the fornt have effected the data at the backend. I did not get what u meant by saying separate set of test cases for database?

say if we have objects like an update button or add or delete button etc., then we will be preparing test cases for the operations of these type of buttons and thus the database testing related test cases are also prepared.... any one can correct me if i am wrong...

Hi Frendz,

Whenever we are doing databaseb testing, it is just to save the time while doing the manual testing mostly from the fron end (UI of the application). We have to write the triggers, scripts, stored procedures etc to validate the data and the functions of the application which we are going to test from the backend.

In this way, we will save much of the time and test cases have to be written for that. The difference between the test case preparation when we are doing the testing from the front end and when backend is that in the backend/database test case preparation, we have to write the scripts, procedures in the Test Data column of the test cases to reperesent the functions through these procedures, triggers or scripts etc.

Nikhar Chugh

based on client requrment or SRS

Feature to be tested = things not importent for the application
Eg. performance testing for desktop application

features not to be tested= things must be cheched.
Eg: all functinal testing etc

Some of the things that comes specifically under database testing are namely
Checking of optimisation of paths
Execution plans of database
Triggers used
Utilisation reports and so on

can anyone say what r the CR tools

Hi Naveen,

To be very clear, "Features to be tested" section in the Test Plan means all the features which are probably going to be tested by the testing team.

"Features not be tested" simply means that these features are also a part of teh software which we will be relaesing to the customer but the testing of tehse features is out of the scopr of the etsting process to be done by the testeres and hence testing of these features will not be done in this release

Hope this clarifies the situation.

Thanks,
Nikhar

You should be able to figure out features to be tested and features not to be tested if there's any documentation provided or if there's any legacy application,the error prone arears can determine what to be tested.I'm a junior tester but I think it all depends on the risk and cost of the application.

Hi,
Database testing is the backend testing. When we enter the data in the frontend that stores in the database. Database testing is used to check the data consistency and integrity. For Ex. when we enter the first name in the frontend it should store the first name field of the database. Like functional testing we write separate testcases for the backend testing. If it is a SQL database we use SQL management studio to write the queries and retrieve the data to check the consistency. If it is a Oracle database we use toad to write the queries.

2. Items or features to be tested and items or features not to be tested in the testplan.
Testplan means planning the whole testing process. As we all know well, we can't test the whole application at a time. so we schedule them in builds when we prepare the testplan. Like items or features to be tested in the build1 and items not to be tested in build1 and so on.


Thanks,
Purni.