Like QTP, we can code/Script for application that is not developed yet. There is a special type of programming style call as Descriptive programming.
I want to know Test partner supports the same or not ?
Yes, it is called "raw attach" in TestPartner. Example:
assumes that there is an object "MyWindow" in the object map. But you need an application to create objects in the object map. If you do not have the application yet, but you know that the window title will by "My Apps Main Window" you can identify the window by:
Window("Caption='My Apps Main Window').Attach
or if you know the name of the .exe file of your app:
This searches for a window which belongs to the process myapp.exe.
If your app is implemented in .NET, Java, VB or any other language which exposes object names you can use those names to identify the controls of your app, e.g.:
to write the text "tester" in the edit box with the Name "edtLogon".
We generally used DP [img]/images/graemlins/smile.gif[/img] (Descriptive Programming) in QTP to avoid Object Repository(QTP)or object Map(in TP). we just create objects and avoid repository..cuz the repository and the object maps suck and they break often or get corrupted.
Developing automation scripts before the application is deployed is possible, but I dont know If ever anyone did it. With my expertise I cannot..not yet.
This is the principle though....
we need documentation from the dev team ( tech specs?) about the naming conventions of the objects and the way the objects will be placed and their properties etc. With that document, we can know about the differant objects and can develop our automation code. Once the APP is ready, we might have to polish our code...But, it can work....
Finally..I think this is possible in TP also...QTP does not support it nor does TP.
We can leverage either of the tools and get it done...