Closed nalanj closed 12 years ago
@commondream You are on a roll! I was wondering about autocomplete and came in to see the if it was already reported, and bam! You just had fixed it!. It's working great for me!
:+1: Awesome! What do you think of tconsole so far, now that you can actually use it?
So far, I like it a lot! My Gemfile is quite extensive and running individual tests was way to slow.
For a while I was using spork, but it requires a lot of configuration, special stuff for devise, etc. When I upgraded to rails 3.2 it completely stopped working for me, so I started looking elsewhere.
I then switched to spin, which is good, but the workflow is a bit of a pain since you run the test in one terminal, but the output of the test is displayed in terminal that started the server, so you have to keep switching between them.
So far, tconsole seems to be exactly what I wanted!
Now I just need to get used to the minitest output format, which actually looks pretty nice.
I've been working to customize the mintiest output to be as helpful as possible, so let me know if there's anything else I can help you with on that front.
You may be interested in this quick screencast I posted today - it covers some of the latest tconsole features, which you may or may not know about: http://commondream.net/blog/2012/02/24/tconsole-1-dot-1-preview/
Good screen cast! That definitely clears up what the numbers are for. Keep up the good work!
@commondream I thought you'd like a bit more feedback:
I have been using tconsole for the last few days and I am really loving the workflow. My tests are running much faster (especially since I am also trying out ruby 1.9.3).
What has really been great, is combining it with pry. With spork or spin, I could not really use a pry breakpoing (or ruby-debug for that matter) for those hard-to-debug tests, but with tconsole, it works just fine. The pry session is started in the same terminal and I can debug to my heart's content.
Thanks again!
@ylansegal That's great to hear! Let me know if you think of any ways that I could help make your testing workflow even better!
Now that we're using classes and methods we need to be able to autocomplete against them.