Okay I maybe asking a foolish question here but please bear with me and answer if you know. I am looking into ODT testing because I read one of its advantage is that this type of automation testing does use excel or csv files with rows of data which can be hard and confusing to maintain instead it uses custom objects recreated from custom test classes to drive the test.
Now I maybe missing a trick here but I have created classes with properties and methods from this classes I have recreated objects.However I fail to see how I would avoid using excel or csv files to drive my script doing it the visual way described in TC7 help is unrealistic since I have about 200 rows of data I would like to test.
Is there a technique I am missing?, how do testers who do ODT testing use this method of testing without having to use csv or excel files but test all the variety of data they want to perform. I don't see myself hard coding 200 objects with all the data I want to test cause I think it will ultimately be confusing. So it seems I still have to use the old csv and excel files.
Anyone with answers would be appreciated? [img]/images/graemlins/confused.gif[/img]
Yes, so NOT having to use excel files or csv files I am shying away cause we have about 50 files, each with about 200 rows of data. Now if ODT can get rid of the excel or csv part of things then how can I do it?. Asking causing so far I can't see how Object driven testing would help me reduce or get rid of the files from what I have learnt so far. If I can't get away from using files then what is the advantage of ODT testing over Data-Driven testing. I once read somewhere on AutomatedQA that ODT testing helps remove confusion of having to maintain files that drive script routines or maybe I read wrong. Thanks for your reply