Talk:IBM Rational Functional Tester

From Wikipedia, the free encyclopedia

[edit] Critisism

Quite bluntly – Rational Functional Tester (RFT) sucks. Common tasks range from difficult to impossible.

Examples as why RFT Sucks:
1. Single stepping through code: Use the "F11"; however "F11" is also used to abort the script, so if you press it out of time, you abort your script.
2. For a given web page; trying to check all properties on the page. Who ever set this up for RFT needs to have his head examined. When I check a box saying I want all children; then I should get all children checked. There is no warning that... oh, some (read all) of the children will NOT be checked. Then the user (me) has to go through and manually check every item, and confirm that they will be tested.
3. Confirm that the given script will run on more than one web site. There currently is a support ticket on this. WHY? This is a common task; run it in test, and confirm in production.
4. Finding where the script errors are located at is difficult (read: Impossible); there is no line to "double click on" that makes any sense.
5. Updating properties: No confirmation and one click and all properties are updated -- no exception. (Example why this is bad: The date changed, this is an issue that is "passed", but the spelling error is a bug; oh, they are now both passed?)
6. The system has problems with what is "30 seconds to time out"; in some instances, 5-10 minutes pass with no time out error generated.
7. The status (logging) window is frequently (always) buried, rendering it useless.
8. When the tool is checking properties, there is no confirmation what is happening. Did the system hang, or is it really doing something – what; how much longer?

competitor or dissatisfied Costumer? Can´t tell ... by the way the comment is longer than the article. If it realy suck that much --193.158.17.135 (talk) 06:13, 16 May 2008 (UTC)