@ m_essaid
Yes, you can manipulate the dataset object.
BUT (and it's a big but)
By doing so, you are NOT testing the application properly. The user does not interact with the dataset object. They interact with the GUI. So if you use methods attached directly to the dataset, which would normally be triggered by interaction with the GUI, then you have failed to test the GUI.
I generally only use the dataset object for reference purposes (such as looking up field names). You should avoid driving it, to drive your test though.
(And without debug info in the compile, I'm not sure you'll be able to access the dataset anyway? If it's a Delphi application ...)
Ah you're just right from the begining to the end.
- I'm not testing the GUI
- I just should use it to navigate through the datas before testing the GUI
- and in Delphi without debug infos... you don't have access to the datas.
To address your three points:
1. If you're not actually testing the GUI, then yes, do everything via the dataset if you want.
2. I'm not sure what you mean here? The GUI is populated via the dataset?
3. Correct. I've just had a quick look at a TwwDBGrid in my Delphi app and the DataLink property is listed in the "Debug" section. So I don't believe you can access it without debug info on.
2) yes, sometimes it is. So it's a way to re-create a test environment by putting the cursor in a specific location, then testing the GUI.
