86 lines
2.4 KiB
Plaintext
86 lines
2.4 KiB
Plaintext
(******************************************************************************
|
|
You got an error, which is exactly as it should be.
|
|
This is the first step in the Test-Driven Development
|
|
(TDD) process.
|
|
|
|
The most important part of the error is
|
|
|
|
"cannot compile"
|
|
|
|
It's looking for a file named uHelloWorld.pas that doesn't exist.
|
|
|
|
To fix the error, create a unit file named uHelloWorld.pas
|
|
in the same directory as the file uTestHelloWorld.pas.
|
|
|
|
The beginning of the new unit file should contain a unit statement:
|
|
|
|
unit uHelloWorld;
|
|
|
|
The new unit should contain Interface, Implementation, and End. statements.
|
|
|
|
The primary focus of this exercise is to provide you with a very simple
|
|
exercise that you can use to test the tools necessary for this language track,
|
|
are working correctly. To that end we are providing you with code that you may
|
|
use as the solution to this exercise:
|
|
|
|
{------------------< start solution >------------------}
|
|
unit uHelloWorld;
|
|
|
|
interface
|
|
|
|
function Hello: string;
|
|
|
|
implementation
|
|
|
|
function Hello: string;
|
|
begin
|
|
result := 'Hello, World!';
|
|
end;
|
|
|
|
end.
|
|
{------------------< end solution >------------------}
|
|
|
|
Hint: Delphi will take care of all this if you instruct it to add a new unit
|
|
to your project. Be sure to save the new unit as uHelloWorld.pas before
|
|
trying to compile again.
|
|
|
|
For more guidance as you work on this exercise, see
|
|
GETTING_STARTED.md.
|
|
******************************************************************************)
|
|
unit uTestHelloWorld;
|
|
|
|
interface
|
|
uses
|
|
DUnitX.TestFramework;
|
|
|
|
type
|
|
[TestFixture]
|
|
HelloWorldTest = class(TObject)
|
|
public
|
|
[Test]
|
|
procedure Say_hi;
|
|
end;
|
|
|
|
implementation
|
|
uses uHelloWorld;
|
|
|
|
procedure HelloWorldTest.Say_hi;
|
|
var
|
|
Expected: string;
|
|
Actual: string;
|
|
begin
|
|
Expected := 'Hello, World!'; //Expected: This is what is expected to be returned by the function/method (Hello)
|
|
Actual := Hello; //Actual: This is what is actually returned by the function/method (Hello)
|
|
Assert.AreEqual(Expected, Actual);
|
|
|
|
//As you progress in this track you will find that not every exercise has Expected and
|
|
//Actual defined as explicitly as they have been above. Often times you may find
|
|
//that the Expected outcome is inserted as an inline statement and the the call
|
|
//to the method being tested will be inserted in the Actual position of AreEqual like so:
|
|
//Assert.AreEqual('Hello, World!', Hello);
|
|
end;
|
|
|
|
initialization
|
|
TDUnitX.RegisterTestFixture(HelloWorldTest);
|
|
end.
|