Torsten Rüger 1a096110a8 basic require_relative (hack)
opted to hack require to be getting on
need require for the test helper
and the files in lib/parfait

General require mechanism would still be ok, but require_ralative means implementing file source, which needs to be dragged around. I'll make an issue
2019-09-07 22:13:53 +03:00
..
2019-02-08 23:03:23 +02:00
2019-08-24 17:00:59 +03:00
2019-09-03 02:02:21 +03:00
2018-05-20 14:45:48 +03:00
2019-08-25 14:40:59 +03:00
2019-09-07 17:56:06 +03:00
2019-08-24 09:46:33 +03:00
2019-09-07 17:56:06 +03:00
2019-09-07 22:13:53 +03:00
2019-09-06 21:02:09 +03:00
2019-08-24 09:46:33 +03:00
2018-06-16 21:01:15 +03:00
2019-09-07 16:43:47 +03:00
2019-08-19 15:23:57 +03:00
2018-07-07 17:34:08 +03:00
2018-08-06 13:07:06 +03:00

Testing

Tdd, Bdd , Xdd, whatever you call it, i have come to the point where it is a way not only to write software, but to think about software. Ie:

  • if it's not tested, we don't know it works
  • test first makes me think about the software from the outside. (good perspective)

I used minitest as the framework, just because it is lighter and thus when the time comes to move to rubyx, less work.

All

'''' ruby test/test_all.rb ''''

Parfait, Risc , Arm , Mom

Follow the directory structure of the source and may be called unit tests

Risc/Interpreter

Contains many system tests that rely on everything else working. Should be hoisted i guess.

Main

Much like the Interpreter test, but for Arm. This is where the currently few executables are generated and there is an automatic way of running them remotely.

The plan is to integrate this with the interpreter directory