Erlang Common Test syntax highlighting on the console? - terminal

Is there a way to get syntax hightlighting on the test results that Common Test prints to the console? I am coming from a Ruby background and I like the way Rspec highlights failed and successful messages differently. Is there an option for this in CT?
Thanks in advance!

Are you using rebar ct to run your suites? I wrote a replacement: https://github.com/rlipscombe/topcat
It has syntax highlighting, to a point. You might find it useful; you might not.

Related

I can not get pigments highlighting for Python to work in my Sphinx documentation

I've tried adding highlight_language and pygments_style in the config.py and also tried various ways I found online inside the .rst file. Can anyone offer any advice on how to get the syntax highlighting working?
Sorry, it turns out that program arguments aren't highlighted (the test I was using)

How to debug quickly in phoenix/elixir?

As I am learning Elixir/Phoenix, I happen to run into an issue like this often.
The problem is that this comes from a dependency, so normally I do this:
open deps/something/.../thefile.ex
add some debug code like IO.inspect to see what params are being passed
stop server, recompile with mix deps.recompile something
check the documentation to see what types are expected to that function
compare the types and trace down the problem to my code
This works but I'd like to improve my process, I know I can use Iex to start a repl, but I'd like to get much faster in terms of:
having a repl inside of the error page itself started automatically (like in better_errors gem for Rails)
having a way to see what arguments went into that method without me digging around (could be solved by the former point)
being able to see a method's documentation quickly
Also any other tips are greatly appreciated.
Please open up an issue in Plug: https://github.com/elixir-lang/plug
You have some great suggestions, like accessing the docs and make the arguments explicit. I don't think we can provide a REPL at the place of error though.
EDIT 1: I went ahead and opened an issue here since I got excited about those improvements! :D
EDIT 2: I realize that I should probably have used a comment as this is not quite an answer (yet!)

TestFirst.org Learn_ruby rake and depreciation warnings :should and :expect syntax

After many searches via Google I'm ready to get some input from the community. I'm trying to apply for App Academy in San Francisco and one of the required pre-work is TestFirst's Learn_ruby. I original had this configured on a Linux VM on my windows box. It worked very well. When I ran rake it would list one problem at a time; the text was is helpful colors; and the output was very condensed so I only got what I needed to read. I've recently wiped and configured my system as a dual boot Xubuntu 14.04/ Windows and the VM I once had is long gone. I worked to get Ruby setup in my linux vm just as I had done in the VM.
My problem now is when I run rake on my projects I get the same depreciation warning:
Deprecation Warnings:
Using should from rspec-expectations' old :should syntax without
explicitly enabling the syntax is deprecated. Use the new :expect
syntax or explicitly enable :should instead. Called from
/home/kaji/Projects/learn_ruby/05_silly_blocks/silly_blocks_spec.rb:25:in
`block (3 levels) in '.
After googling this back and forth I understand for the most part what the error is telling me. And I've even found a solution to get it to go away. Thanks to this post: RSpec's New Expectation Syntax, I was able to find a syntax to make the warning go away. (basicly had to change blah.should == # to expect(blah()).to eq(#) inside the *_spec.rb file. This seems to make the warning happy. However I still see signs that I have another problem.
The output isn't as 'friendly' as it was when I was on my VM. It's not in color; it dumps all the errors at once. What I enjoyed the most about learn_ruby was it gave me one objective at a time with minimal output. Now i have to scroll up quite a ways just to see what my issues are.
I've tired removing RVM completely and all gems and reinstalling to see if I could resolve this. No dice. I'm such a Ruby Noobie i'm a little overwhelmed with all this. I'd like to just get back to learning the basics but this has been troubling me for over a week. Has anyone had this problem/fix the except
I've also tried removing the rpsec ~<=2.0 from the Rakefile. I'm using ruby -v 2.1.2, rails 4.1.1 and i have RSpec 3.0.0, 2.99.0, 2.0.0. I even tried finding a tutorial on changing the syntax but it was real confusing as it introduced lots of Ruby concepts I have no idea on. At that point I feel like I'm over my head and there is something simple I'm missing.
Hope I provided enough info for assistance.
I hope I'm answering the correct question, since you seem to have figured out the one in the title (i.e. the preferred syntax having changed from blah.should to expect(blah).to). It would help if you changed the title to reflect the actual question.
RSpec.configure do |config|
config.fail_fast = true
config.color_enabled = true
}
will make RSpec fail at first error, rather than after running all tests, and enable the colours, for that one file.
Or you can run rspec with rspec --fail-fast --color.
Alternately, you can put this in $HOME/.rspec so it always does it:
--fail-fast
--color

selenium - Unsupported command dragAndDrop with switch to ruby

I have a nice test suite in the selenium IDE using the HTML format.
I wish to change that to ruby.
I try the format change to ruby/rspec but I get
# ERROR: Caught exception [ERROR: Unsupported command [dragAndDrop | xpath=
(//div[#id='external-events']/div[contains(text(),'My Event 1')]) | 300,150]]
Any way to get around this and avoid the error? Do other Ruby formats get around this?
I also dried dragdrop but got the same error.
A lot of the IDE functions are unable to be converted directly into the language of your choice. DragAndDrop is one of them, I don't think it's implemented for any of the exports.
You'll have to use the ActionBuilder:
http://selenium.googlecode.com/svn/trunk/docs/api/rb/Selenium/WebDriver/ActionBuilder.html

Error when trying to run Watir test through Fitnesse

I've recently been trying to run the following tutorial:
http://raveendran.wordpress.com/2010/10/20/watir-integration-with-fitnesse/
However I when I attempt to run the test in Fitnesse, it just sticks on "running test" without ever doing anything. I have tried to replace some of the Syntax, formatting etc but I just get the same result. Does anyone know how successfully implement this tutorial?
Many thanks for any help provided.
Matt
I remember doing that. It was tough to set up correctly. I can't remember much about it, but there was a fixture that helped me at Faucets. Good luck.

Resources