the code chronicles

code or code not .. there is no try jump-to nav: links to stuff Ruby on Rails tunez home

[codechron-blog]

Webcast • The Basics of Git and GitHub • December 2013

Subscribe: http://bit.ly/githubguides • Are you new to Git and GitHub? Would you like to learn the basics but haven't taken the time to read the GitHub Help ...

from the deranged mind of the creator of Linux .. Git and GitHub Version Control System .. makes it all so .. so .. easy ..

a must see tour of the features and workflow .. so dope

[codechron-blog]

[codechron-blog]

test doublin along

The following are the main ideas and links to some info and terminology that helped me understand the test double concept. A Test Double ...

… is the answer to the questions: - How can we verify logic independently when code it depends on is unusable? - How can we avoid Slow Tests? … replaces a component on what a system under test (SUT) depends with a “test-specific equivalent”. here is a great visual representation regarding:

… gets its name from the notion of a stunt double. “When the movie industry wants to film something that is potentially risky or dangerous for the leading actor to carry out, they hire a "stunt double" to take the place of the actor in the scene. The stunt double is a highly trained individual who is capable of meeting the specific requirements of the scene. They may not be able to act, but they know how to fall from great heights, crash a car, or whatever the scene calls for. How closely the stunt double needs to resemble the actor depends on the nature of the scene. Usually, things can be arranged such that someone who vaguely resembles the actor in stature can take their place.” … works like this: “For testing purposes, we can replace the real DOC (not the SUT!) with our equivalent of the "stunt double": the Test Double. During the fixture setup phase of our Four-Phase Test, we replace the real DOC with our Test Double. Depending on the kind of test we are executing, we may hard-code the behavior of the Test Double or we may configure it during the setup phase. When the SUT interacts with the Test Double, it won't be aware that it isn't talking to the real McCoy, but we will have achieved our goal of making impossible tests possible.” … has a few different circumstances in which to use a particular type for our tests:     •    If we have an Untested Requirement that we cannot verify because neither the SUT nor its DOCs provide an observation point for the SUT's indirect output that we need to verify.     •    If we have Untested Code and a DOC does not provide the control point to allow us to exercise the SUT with the necessary indirect inputs.     •    If we have Slow Tests and we want to be able to run our tests more quickly and hence more often.

… has the following hierarchical representation and role descriptions of its main flavors:

Dummy Object

  Purpose: Attribute or Method Parameter

  Has Behavior: no

  Injects indirect inputs into SUT: no, never called

  Handles indirect outputs of SUT: no, never called

  Values provided by test(er): no Test Stub


  Purpose: Verify indirect inputs of SUT


  Has Behavior: yes


  Injects indirect inputs into SUT: yes

  
Handles indirect outputs of SUT:  ignores them


  Values provided by test(er): inputs



Test Spy


  Purpose: Verify indirect outputs of SUT


  Has Behavior: yes


  Injects indirect inputs into SUT: optional


  Handles indirect outputs of SUT: captures them for later verification


  Values provided by test(er): inputs (optional)



Mock Object


  Purpose: Verify indirect outputs of SUT


  Has Behavior: yes

  
Injects indirect inputs into SUT: optional


  Handles indirect outputs of SUT: verifies correctness against expectations

  Values provided by test(er): outputs & inputs (optional)



Fake Object


  Purpose: Run (unrunnable) tests (faster)


  Has Behavior: yes

  
Injects indirect inputs into SUT: no


  Handles indirect outputs of SUT: uses them


  Values provided by test(er): none

Temporary Test Stub


  Purpose: Stand in for procedural code not yet written


  Has Behavior: yes

  
Injects indirect inputs into SUT: no

  
Handles indirect outputs of SUT: uses them

  
Values provided by test(er): none

[codechron-blog]

FYI .. i will be sprinkling in more than a little bit of my first love .. music.

why in the world would i do this? because i cannot think straight without it?!?! soooo since eargasmic tracks are a must when i jack into the matrix .. they will be a must while i write about it .. soooo stay tuned for, IMO, the sickest genre-traversing, head-noddin, hip-swayin vocals, melodies and beats ..  enjoy or ignore .. your choice.

[codechron-blog]

strap up homie! 

after trying a bunch of different combinations of dev tools, the following are my weapons of choice:

MacBook Air 11-in - 1.3G Intel Core i5 - 4G 1600 MHz DDR3 

OSX v 10.8.4

Rails 4.0.0

Ruby 2.0.0p247

Sublime Text 2 v 2.0.2

Base v 2.4.6

*honorable mention to the codelearn playground when working on computers that are not yours. it includes a browser based Terminal, File Browser, Code Editor and App Output.

[codechron-blog]

ok .. "i'm ret ta go"

Who: you can call me esskay /iˈskā/.

What: chronology a of my efforts to become a full stack dev (i.e. an all-singing, all-dancing technical wizard of the software development persuasion).

When: updates will be posted as often as i can.

Where: same bat channel.

Why: to log my adventures in code land .. and to satisfy a challenge assignment for the supadope rails bootcamp that i am currently in. 

.. big ups to the tealeaf academy krew!

ps .. although very much capable .. i rarely use proper punctuation when keyboarding .. pardon my swag .. thanks much :)