推荐一款 API 自动化测试工具——Runscope

目前很多业务都是前后端分离来做，后端负责写API，如我司RightCapital后端用Laravel5.3来写API供前端AngularJS来消费。写完API需要自动化测试，这里推荐Runscope这个自动化API测试工具，这里是它的features:Runscope Features，当然，这是收费的，但是能极大提高生产率呀，这点就是小钱了，何况程序员都很懒，能自动化的东西就自动化。Runscope是个Web App，类似于Postman但远超Postman，这里截个工作页面图，是个人的，我司的就不放了：

Runscope能干啥呢？太多了，API Monitoring, API Testing, Real-time Traffic Monitoring, Traffic Logging and Debugging。个人比较懒，具体功能就不详述了，看看文档：Runscope Docs。
Runscope能安装一些插件，如HipChat,Datadog等，我们这边是使用HipChat来接收Runscope测试监控API时的消息，还很方便。

这款软件已经在我司长时间使用了，经过检验，是个效率神器，而且它的好多功能还没被压榨出来呢呢，以后个人再慢慢探索慢慢压榨。这里推荐感兴趣的可以关注下这款软件。

这里有我司的技术栈，有共同爱好者可以相互交流下，当然有意愿Join的速来Profile：Join RightCapital

from : https://laravel-china.org/topics/2926

Take a BITE out of Bugs and Redundant Labor

In a time when more and more of the web is becoming streamlined, the process of filing bugs for websites remains tedious and manual. Find an issue. Switch to your bug system window. Fill out boilerplate descriptions of the problem. Switch back to the browser, take a screenshot, attach it to the issue. Type some more descriptions. The whole process is one of context switching; from the tools used to file the bug, to gather information about it, to highlight problematic areas, most of your focus as the tester is pulled away from the very application you’re trying to test.

The Browser Integrated Testing Environment, or BITE, is an open source Chrome Extension which aims to fix the manual web testing experience. To use the extension, it must be linked to a server providing information about bugs and tests in your system. BITE then provides the ability to file bugs from the context of a website, using relevant templates.



When filing a bug, BITE automatically grabs screenshots, links, and problematic UI elements and attaches them to the bug. This gives developers charged with investigating and/or fixing the bug a wealth of information to help them determine root causes and factors in the behavior.



When it comes to reproducing a bug, testers will often labor to remember and accurately record the exact steps taken. With BITE, however, every action the tester takes on the page is recorded in JavaScript, and can be played back later. This enables engineers to quickly determine if the steps of a bug repro in a specific environment, or whether a code change has resolved the issue.

Also included in BITE is a Record/Playback console to automate user actions in a manual test. Like the BITE recording experience, the RPF console will automatically author javascript that can be used to replay your actions at a later date. And BITE’s record and playback mechanism is fault tolerant; UI automation tests will fail from time to time, and when they do, it tends to be for test issues, rather than product issues. To that end, when a BITE playback fails, the tester can fix their recording in real-time, just by repeating the action on the page. There’s no need to touch code, or report a failing test; if your script can’t find a button to click on, just click on it again, and the script will be fixed! For those times when you do have to touch the code, we’ve used the Ace (http://ace.ajax.org/) as an inline editor, so you can make changes to your javascript in real-time.

Check out the BITE project page at http://code.google.com/p/bite-project. Feedback is welcome at bite-feedback@google.com. Posted by Joe Allan Muharsky from the Web Testing Technologies Team (Jason Stredwick, Julie Ralph, Po Hu and Richard Bustamante are the members of the team that delivered the product).

reference : http://googletesting.blogspot.com/2011/10/take-bite-out-of-bugs-and-redundant.html