I assume everybody knows about Embarcadero ( a.k.a Borland ) and their product:
Delphu and C++ Builder.
I think that WineHQ could be tested just fine using Delphi Handbooks provided source code + shipped Demos with each RAD Studio release.
Why? - I suppose you exceatly can trace what function in what circumstances fails and simply add the function with needed changes to corresponding Header file.
I would recommend to use code snipps in:
- Mastering Delphi 7.pdf ;
- Delphi 2010 Handbook by Marco Cantu and the Code examples, downloadable @ Embarcaderos EDN article.
As I am now thinking about possible project using Delphi XE and IntraWeb 11, it would be good testing platform for WInes web capabilities ..
Possible test-cases with code and backtrace capabiliets
-
- Level 2
- Posts: 11
- Joined: Thu May 19, 2011 12:16 pm
-
- Level 2
- Posts: 11
- Joined: Thu May 19, 2011 12:16 pm
One related question:
What problems may occur for project aimed to provide automated testing tool for particular Delphi / Lazarus projects based on this Application functionality:
1. Browse the Delphi / Lazarus project;
2. Compile it;
3. Run GUI / CLI tests and log all errors found during run-time;
4. Generate file containing full winedbg-like syntax for error / warning / fixme lines.
I think it would save a lot of time doing monkey-job ...
What problems may occur for project aimed to provide automated testing tool for particular Delphi / Lazarus projects based on this Application functionality:
1. Browse the Delphi / Lazarus project;
2. Compile it;
3. Run GUI / CLI tests and log all errors found during run-time;
4. Generate file containing full winedbg-like syntax for error / warning / fixme lines.
I think it would save a lot of time doing monkey-job ...
I'd say do a few by hand before concluding it's time
to automate. But once it's time to automate, yeah.
See also http://wiki.winehq.org/UnitTestSuites
to automate. But once it's time to automate, yeah.
See also http://wiki.winehq.org/UnitTestSuites
-
- Level 2
- Posts: 11
- Joined: Thu May 19, 2011 12:16 pm
Oh, Okay, I will try.
Anyway, here is a bit info I may want to publish for myself to remeber and other to have some insight ... or even push to join / continue my idea.
So, what could be used for such tests is BuildBot projects forvided automated testing environment.
Then, we use Profiling to trace performance and analyzize unknown calls to any code structure / file using this utility: SimpleProfiler1.7.7
---
After the project has been built, the utility could be-auto-attached to test it under runtime. Once testing is done, GUI encapsulating the buildbot and simpleprofiler would be ended and output file would be created.
Maybe people @ Lazarus IRC are interested in this ...
Anyway, here is a bit info I may want to publish for myself to remeber and other to have some insight ... or even push to join / continue my idea.
So, what could be used for such tests is BuildBot projects forvided automated testing environment.
Then, we use Profiling to trace performance and analyzize unknown calls to any code structure / file using this utility: SimpleProfiler1.7.7
---
After the project has been built, the utility could be-auto-attached to test it under runtime. Once testing is done, GUI encapsulating the buildbot and simpleprofiler would be ended and output file would be created.
Maybe people @ Lazarus IRC are interested in this ...
