6 years ago, the good folks over at Wufoo held an API contest in which the first prize was a friggin’ battle axe. I thought that was absolutely brilliant on their part and I was positively jealous of how creative their idea was. Ever since we’ve had a public API for Lean Testing I wanted to do something similar. But obviously we couldn’t do it unless we had something more badass to give away than a friggin’ battle axe. Let’s just say that was hard to beat.
Here are two recent Lean Testing news we thought you should know about: Version 3.0 is now live for all users We’ve added a ton of new features in version 3.0. Here are just a few of them:
By popular demand, we’ve now enabled Markdown in Lean Testing. What is Markdown? Markdown is a very simple way to add formatting to your text. You can use Markdown syntax to format the content of your bug reports, test cases and messages in the Conversation page. In this blog post, I will be providing the basic elements of Markdown. Here are some elements to help you start: You can make text “italic” or “bold” by using *italic* and **bold** or _italic_ and __bold__ You can create lists by simply adding a dash – before the list elements, as such: – First element – Second element – Third element And you can create a checklist as such: [x] First item, checked [ ] Second item, unchecked [x] Third item, checked Links are automatically generated when URLs are detected, and you can link to bug reports by simply adding the pound sign # before their number (Example: adding #20 will link to bug report number 20) Most excitingly, you can now use code blocks: To add a code block, start by adding ~~~ before and after your code: ~~~ $form = $this->beginWidget(‘bootstrap.widgets.BsActiveForm’, array( ‘layout’ => BsHtml::FORM_LAYOUT_HORIZONTAL )); ~~~ Using these tips opens up a tremendous amount of […]
If you’ve been around long enough, you’ll remember that our first foray in test case management at Lean Testing was through the acquisition of Overlook.io, which we operated as a separate entity for a little while. Well, we quickly realized that managing two separate tools was not optimal for us or for our users, so we merged what was then our “bug tracking tool” known as Damn Bugs with Overlook.io to create Lean Testing: a comprehensive test management solution. The initial version of our test case management system was fairly limited in scope and functionality. To be perfectly honest, it was an experiment. We had no idea if and how it would be used by our users. However, we liked the idea of a bug tracker and a test case manager in the same tool. Fast forward to a few months from now, we realized that over 10,000 test suites and over 130,000 test cases had been created in our test case management tool. That was validation enough for us to start working on a new and improved version of our test case management system. Last night, after many months of hard work, we released a completely new version of […]
You can now enable status updates in GitHub and Bitbucket on a per-project basis. To do so, follow these simple steps: Connecting Github and Bitbucket with Lean Testing: Go to the project’s management page and connect your GitHub or Bitbucket account. From there, select the repository and the branch you want to link to your project. Changing bug status updates via commit messages: The Github and Bitbucket integration allows repository committers to change bug statuses by embedding specific commands into their commit messages. You simply need to add the bug number and desired status between brackets [ ] in your commit. For example: And voilà! That is how you enable bug status updates, and they will be updated automatically in Lean Testing.