On Mon, Dec 19, 2011 at 5:26 AM, Graeme Geldenhuys
wrote:
> On 17 December 2011 18:03, Luciano de Souza wrote:
>> The idea of FPCUnit is really wonderful. I really would like to use it, but
>> Lazarus dependencies can complicate a lot.
>
> I have been a long time user of FPCUnit and even helped t
On 17 December 2011 18:03, Luciano de Souza wrote:
> The idea of FPCUnit is really wonderful. I really would like to use it, but
> Lazarus dependencies can complicate a lot.
I have been a long time user of FPCUnit and even helped to maintain
and improve it over the years. It has some design flaws
On 17 December 2011 18:33, Michael Van Canneyt wrote:
>
> The necessary functionality is contained in the consoletestrunner unit.
I have long ago said this must move to the FPC repository, not live in
the Lazarus repository.
--
Regards,
- Graeme -
_
You would believe if I told you I could not compile yet?
It's not lack of effort, believe me. I really can't understand what is
failing.
See my compilation script:
@echo off
set compilerpath="c:\lazarus\fpc\2.4.4\bin\i386-win32\fpc.exe"
set unitpath="-Fuc:\lazarus\fpc\units\i386-win32\*
-Fuc
On Sat, 17 Dec 2011 17:47:49 +0100
Felipe Monteiro de Carvalho wrote:
> On Sat, Dec 17, 2011 at 5:03 PM, Luciano de Souza wrote:
> > I can compile using callings like:
> > fpc test.pas
> > fpc -XX test.pas
> > fpc test.pas -Fu./pas -FE./exe
>
> You can compile Lazarus projects in the command li
On Sat, Dec 17, 2011 at 5:03 PM, Luciano de Souza wrote:
> I can compile using callings like:
> fpc test.pas
> fpc -XX test.pas
> fpc test.pas -Fu./pas -FE./exe
You can compile Lazarus projects in the command line using lazbuild
which comes with Lazarus, like this:
lazbuild project.lpi
It will
Michael,
I have a meaningful peculiarity: I am blind and I use Freepascal only in
the console interface, reading all the output by means of my screen
reader. Lazarus and Freepascal console IDE are both inaccessible. But,
fortunately, for me, it's easy to call the compiler passing parameters
a
You see no test results, because the program file of your test
application is missing some essential things.
If you are using lazarus, simply create a new testing application:
First, make sure that package fpcunitide is installed.
Then, in the 'File-New' dialog, your testproject should be of
The article is very good, but it does not focuse on all aspects.
I have tried to create my first test example, but it didn't work. The
compilation is successful and the program is executed without errors.
However, I received no messages, informing the test has failed.
Actually, the test should
Perhaps becouse I am not an experienced programer, but the code sounds a
little complex. However, the effort will bring large bennefits.
Thank you very much for the article. It will help me a lot.
Em 16/12/2011 11:44, Michael Van Canneyt escreveu:
On Fri, 16 Dec 2011, Vincent Snijders wrot
On Fri, 16 Dec 2011, Vincent Snijders wrote:
2011/12/16 luciano de souza :
Hello listers,
Navigating in FPC source codes, I found fpcunit. It's really
wonderful. With the tTestCase class, we can generate a report with
the success or the failure of our tests.
Is there documentation on the u
2011/12/16 luciano de souza :
> Hello listers,
>
> Navigating in FPC source codes, I found fpcunit. It's really
> wonderful. With the tTestCase class, we can generate a report with
> the success or the failure of our tests.
>
> Is there documentation on the usage of fpcunit? What is the best way
>
Hello listers,
Navigating in FPC source codes, I found fpcunit. It's really
wonderful. With the tTestCase class, we can generate a report with
the success or the failure of our tests.
However, only observing the source code, it's not easy to comprehend
how it works. I found a single parcial exam
13 matches
Mail list logo
