Viewing profile — maramono

It depends on the difficulty of the bug(s) that need to be localized and fixed. I use a wide range of techniques from simple printf's all the way to a full-blown methodology that h…

I've used it several times but the big problem with it is that once you have a nice, correct model that has been checked (and no counterexamples found), there's no way to translate…

Does your team use a dedicated test (non-developer) team? What has your experience been with them? Do they add value? Do you find yourself questioning or being impressed by their s…

IMO, first we need to solve the smaller issues, most importantly to have developers start making high-quality software consistently . There is nothing that will get solved with the…

If you're already considering leaving, I would take a gamble and tell your CTO/boss exactly what you said and be honest with your employer. Who knows, maybe they trust and respect …

To produce high quality code you need to change your mindset. No tools will help you if you don't know how to use them. Also you cant simply "pass the buck" (so to speak) to tools …

Here's what I use to develop Mutator's [0] and TestLess' [1] GUIs: - implement in Ruby - compile to Java using Warbler/JRuby - Run as Java on any platform that supports Java. You c…

Crazy idea: stop usng mocks completely where possible, and install a formal currency process for keeping the existing ones up to date. Mocks are notorious for diverging from the co…

There are many dimensions to programming languages that range from systems to scripting, weakly typed to strongly typed, dynamic to static typed, purely functional to statefull, im…

What I find interesting is that there is absolutely no mention of the word 'test' in the spec. With unit testing and TDD/BDD so ubiquitous now, perhaps new languages should be crea…

There are methods that can be applied to software that formally prove properties of software so that those pieces are free of bugs. These are called formal methods and require heav…

TL;DR: Matt Wayne (the interviewee) talks about a basic problem that agile was supposed to solve: creating software that actually satisfies business requirements. For him, Cucumber…

Nice title! And a related article: http://time.com/3933976/myths-fourth-of-july/

>> A "hybrid" solution may work well for you—group your tests into small sets, then run the sets sequentially, doing as much of each set in parallel as possible. Very true. In fact…

Related: great article on code inflation https://www.computer.org/cms/Computer.org/ComputingNow/issue...

Very interesting! I assume that most of the smells that are introduced with new files is due to the experimentation that developers perform to solve the problem at hand. Then once …

I can strongly relate to this experience too. As the founder of Ortask, my company is not successful by Silicon Valley measures, but it is successful in my terms because it makes m…

Even though TestLess is intended for automated tests, the technology behind it can be used to compare manual tests. In fact, labs results using several manual test corpora show tha…

Ha! The name TestLess was chosen to imply that without redundant tests, you will be testing less. Unfortunately I did not become aware of the colloquial meaning until after naming …