-
-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To develop a new exercise that features Delphi UI building capabilities #91
Comments
I am looking for the project that 'touches' on testing a UI with DUnitX and so far I have not been able to find it. 😞 |
I have not found an example project that utilizes the testing of a gui. But I have come across some examples of how to invoke a gui from a console app in order to make calls into the UI. This is not a standard practice. Typically the UI and the underlying logic are only loosely coupled. The unit tests are typically geared towards the underlying logic. Test can be written to create an instance of a UI (though it will not be visible) and then simulate clicking on buttons etc. The results created by the simulated clicks can then be compared against the expected result to determine pass/fail of any given test. The question I have: Should the exercise provide the UI ( Does this make sense? |
I won't likely be available until Sunday to spend some time on this, but I think it is a worthwhile endeavor. |
@kotp that's fine. I am not necessarily looking to schedule a time to work on this (yet), just wanting to do some brainstorming on the direction and nature this type of exercise should/could take. |
I have created repo Calculator for the development of this exercise. |
@kotp lets start a conversation about creating a new exercise that would feature Delphi's user interface design capabilities. In passing you've mentioned a calculator program. This sounds pretty do'able, assuming the calculator doesn't get too complicated (feature filled). There is an example project with DUnitX which touches on testing a UI. I'll leave it at that for now....
The text was updated successfully, but these errors were encountered: