Showing posts with label rakefiles. Show all posts
Showing posts with label rakefiles. Show all posts

Thursday, January 26, 2017

LRTHW Exercise 48 in under 37 lines!

It took me a while, but I just worked through the steps and solved all the problems one by one.






Monday, January 23, 2017

Project Complete!


I have finished re-writing my text adventure game, Tree House Prince, available here: (https://github.com/clockworkpc/tree-house-prince)

It is a very simple game, but I am proud of all the things I learned to get it into this shape.

The game demonstrates my grasp of conditionals, classes, inheritance, and automation testing.  Every scene in the game has full module testing in Rakefile; the integration testing has to be done manually at this stage.  (I will learn about that soon!)

Wednesday, January 18, 2017

Getting the Hang of Rakefile!

There seems to be an error every step of the way, but, inch by inch, I'm getting there.


Tuesday, January 17, 2017

User Testing Update



I've had to hit the books again to improve my understanding of variables, classes, and methods.

I've been re-writing my text adventure game so that every aspect of it is tested by the Rakefile.  This means that I have had to extrapolate the logic of the enter() method in each class, so that a test can be written for it.

The most interesting parts of the game involve somewhat complex conditionals, written as case conditionals, and for some reason it took me a while to understand how to pass on a variable to the method containing a case conditional.  Now that I look at it again, it's very simple, but c'est la vie.

Anyway, the re-written game is nearing completion and the latest code is up on Github.

Wednesday, January 11, 2017

Ruby Hack Night Review (2017-01-11)

The first Melbourne Ruby Hack Night, hosted by REA Group, was every bit as good as I had hoped.

Check out Ruby and Rails Melbourne on Meetup.
It was my first proper hacking event since my Linux Victoria days, and it was exciting to sit in a room full of people who really enjoy their code.  The atmosphere at the event was the right mix of serious keyboard tapping and light-hearted conversation, and the venue is really quite comfortable.

We started at 18:00 and worked each of us fairly quietly for about an hour, until the pizzas were delivered.  We downed tools and enjoyed some good food and friendly conversation.  After doing the schmoozing rounds, we drifted back to our computers, and the evening passed by pleasurably and productively until the end of the evening at 21:00.

I was especially pleased to get some much needed help with my test automation, and my vastly improved code will be ready for a push to Github tomorrow, once I've tidied up some loose ends.

(Update: The next version of the code I was working is available)

Many thanks to the organisers and I'm looking forward to the next Melbourne Ruby Hack Night.


Monday, January 2, 2017

Getting started with Rakefile and testing

Up to chapter 47 of Learn Ruby the Hard Way, and I have uploaded version 0.01 of my little text adventure, Treehouse Prince.

https://github.com/clockworkpc/treehouseprince/tree/master/skeleton

The purpose of working on this is to familiarise myself with the fundamentals of testing.  As I put back all the components of the game, I shall get to see how the Rakefile saves me running the game manually a thousand times over.


Monday, December 26, 2016

Ruby Project Skeleton Generator on Gist!

Exercise 46 of Learn Ruby the Hard Way gives instructions for manually creating a project skeleton.  So I decided to do what I have done many times before in BASH and Python, and automate this task with a pretty Ruby script.

A few thoughts:
  1. Ruby's handling of files and folders is delightfully straightforward.
  2. Ruby handles strings elegantly.
  3. This was originally written as a straight script, but then I refactored it with object-oriented programming in mind:
    1. One Class (Project)
    2. The main components of the class broken down into methods.
    3. Names of folders and files are stored in an array and a hash.
    4. Blocks of text are stored using Squiggly HEREDOC

1,050 hours

It took me 13 working days to complete my first 100 "work" pomodoros as a Junior Software Tester at Profectus Group.  Much of ...