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 […]
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.
Whenever I talk about Lean Testing with a user, they always mention how much they love our browser extensions. Much like Lean Testing itself, the browser extensions were built with simplicity and ease-of-use in mind. Moreover, today we’re announcing that this same method of bug reporting is coming to iOS, thanks to our friends at Digital Krikits. In-app bug reporting for iOS: installation process When you create a new project in Lean Testing, you will now be asked what type of project it is. If you specify that your project is a mobile app, a new option will appear in the upper right corner of your screen: Your development team will need to follow the simple instructions provided on this page to add the SDK to your iOS app. It is a simple matter of drag and drop and copy pasting one line of code into your app. You then compile a new build and send it to your test team. In-app bug reporting for iOS: reporting bugs Once your testers have received the new version of the app, they can trigger the bug reporting process by taking a screenshot inside the application. Read How to take a screenshot on your iPhone, iPad and iPod […]
A lot of organizations run into difficulty evaluating their software testing approach. Others often ignore the process altogether. The problem with testing is that it is difficult to quantify. However, without proper analysis and evaluation, it is all but impossible to improve your efforts. Continuous improvement is something every team should strive for. That begins with first identifying and then rectifying gaps in your testing approach. Analyze Defects Found in Production To begin the evaluation process, the best way is to look at bugs or defects that have been identified post-release. Analyze each one and categorize the bug based on which area or part of testing it should have been identified within. For instance, if the issue is related to a new feature you just added, it probably should have been spotted during functional testing. Bugs that crop up in older parts of your app most likely belong to the regression testing category. In addition, seemingly random bugs could be classified under exploratory testing. While no app of any reasonable size will be without defects, the aim of this step is to look for patterns in your testing. Categorizing defects should shed light on the areas that need the most improvement. […]
There’s a perception that game testing involves goofing around and playing games. However, it takes serious discipline and skill to be a good game tester. There are a number of challenges in game testing that you won’t find in standard software testing. Factors that are less tangible than functions and features. Usability testing is complicated due to the need for games to be fun, balanced and to pack an emotional punch. It’s not unusual for developers to get frustrated when investing in a game tester. The line between defect and suggestion can become blurred. Many testers are already eyeing up a career in design or code, and they’re keen to show initiative. Developers just want bug reports, not a critical analysis of the game play. However, if you don’t listen to testing input from your game tester on things like fun factor, balance and emotional impact, then you’re missing out on valuable feedback. Set clear boundaries and categories It’s important to make responsibilities clear at the outset. Make sure that it’s easy for testers to categorize their bugs and suggestions correctly so developers can filter for them. Balance issues, or AI flaws, that may not constitute defects in the strictest sense should still […]