Results 1 to 14 of 14

Thread: Regarding Test Plan

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Junior Member
    Join Date
    Apr 2006
    Answers
    1
    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

    Last edited by jainbrijesh; 05-23-2007 at 03:02 AM.

  2. #2
    Junior Member
    Join Date
    May 2006
    Answers
    1
    Quote Originally Posted by naveenkpatil
    Hi all,
    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.


  3. #3
    Junior Member
    Join Date
    May 2006
    Answers
    5

    Re: Regarding Test Plan

    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,


  4. #4
    Hi,

    Hw r u Friends ? Let me is anything special.



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

    Last edited by jainbrijesh; 05-23-2007 at 03:04 AM.

  5. #5
    Expert Member
    Join Date
    Apr 2006
    Answers
    124

    Re: Datebase Testing

    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...


  6. #6
    Junior Member
    Join Date
    Sep 2006
    Answers
    10

    Re: Regarding Test Plan

    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


  7. #7

    Re: Regarding Test Plan

    Quote Originally Posted by naveenkpatil View Post
    Hi all,
    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
    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


  8. #8
    Contributing Member
    Join Date
    Jul 2006
    Answers
    93

    Re: Regarding Test Plan

    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


  9. #9
    Junior Member
    Join Date
    Sep 2006
    Answers
    10

    Re: Regarding Test Plan

    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


  10. #10
    Junior Member
    Join Date
    Nov 2006
    Answers
    6

    Re: Regarding Test Plan

    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.


  11. #11
    Junior Member
    Join Date
    Oct 2006
    Answers
    10

    Re: Regarding Test Plan

    can anyone say what r the CR tools


  12. #12
    Junior Member
    Join Date
    Jul 2008
    Answers
    1

    Re: Regarding Test Plan

    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.


  13. #13
    Junior Member
    Join Date
    Jan 2009
    Answers
    2

    Re: Regarding Test Plan

    Database Testing : by having a knowledge of database , one can have the idea of whether a data we are saving at in front end is getting saved in proper back end fields . No need to right a test case for data base testing , using sql statement one can retrieve the saved data

    Features to be tested or not tested : this case will applicable very much in case of product development , here version wise build will be there & features priority will be decided , there features will be tested or not tested depending on marketing requirement.


  14. #14
    Junior Member
    Join Date
    May 2010
    Answers
    4

    Re: Regarding Test Plan

    Features to be tested: Featueres that are related to current release of product should be tested

    Features not to be tested:Features that are not related to current release of product cannot be tested.

    Hope this helps


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact