Reply to thread

Message: [QUOTE="Phlip, post: 4635288"] Tx, but it sucks! Here's the ideal test case (regardless of its .should or it{} syntax: test_activate x = assemble() g = x.activate() g == 42 end The test should simply reflect the variables and values of everything after the activate line. Anything less is overhead. I _only_ want to spend my time setting up situations and equating their results. No DSLs or reflection or anything! Now, why can't our language just /do/ that for us? It knows everything it needs... [/QUOTE]