Tag Info

Hot answers tagged

6

For the REST service testing Postman and HttpMaster are good tools. It supports dynamic parameters, validation of response data, various data viewers, etc. If you are looking for performing load testing of the REST services than Grinder and JMeter open source tools can be considered. This data is taken from the post Tools for REST webservice testing


5

As Bookeater says, you absolutely want to unify tools and processes between the teams. That said, I'm going to offer some extra advice because I've been in this situation (and to some extent I am still in this situation). Hasten slowly - Each team has built up a process and toolset that works for them. A newcomer telling them they have to change everything ...


3

I once tested a Windows client UI by randomly banging on the keyboard while my coworker randomly moved and clicked the mouse. I found bugs that way, and I could reproduce them, but (at least initially) I couldn't tell you the exact set of keystrokes and mouse clicks that triggered the problem. That is monkey testing. Exploratory testing is testing ...


3

Timebox it and afterwards evaluate. I would say time-box one hour and then see how probable it is the tester will find the steps to reproduce the issue. Often its easier for developers to reproduce the issue, since they understand the code for that part. And they are more proficient in code-debuging.


2

What are the most important components/parts of a well-written test plan document for a testing project. Consider you are testing a Financial web app. As per IEEE 829 standards, the components of a Test Plan document should be : Test Plan identifier References Introduction Test Items Risks Items to be tested Features excluded for testing Testing ...


2

You are SO going to hate this answer. It is Yes and Yes. There is some possibility to integrate between TFS and fogbugz. http://www.fogcreek.com/fogbugz/docs/70/topics/sourcecontrol/setup/TeamFoundation.html Your goals should be: Maximum tool level integration (to input info only once). Define overlap between procedures and utilize this Minimize ...


2

It depends. I saw acceptable time/effort ranging from 0 (outsourced testing to almost un trained testers) to infinity and beyond (combined engineering team with engineers that know their way through the code and product). YOUR answer will vary according to (just throwing some ideas): Your skills and knowledge e.g. how familiar are you with the product, ...


2

Testcase format I like one of the following formats: Arrange Act Assert Given When Then These give a clear separation between test phases and steps. How is the test situation setup What is the action under test (try to keep action steps under 10, preferable less) What is verified Details How to write the step details of test-cases greatly depends ...


1

I've seen this kind of specifications in companies where their users are provided with specific devices, as for example, doctors inside a hospital to access to the patients clinical registers... because they know that the app (or web) will be used only for a reduced set of devices. Another example, is when you are focusing on a specific market (China, US, ...


1

I would suggest using an open source tool such as http://www.soapui.org/ This will allow you to send requests to your end points and, in turn, see the responses. Should you choose to extend your test from manual into automated (ie run the same test again along with other tests) then SoapUI also gives you that option.


1

Firstly, I would like to start with the Bug Tracking tools. What about the old bugs logged? If you ask one of them to move to the same tool, their information (bug history)is lost. But, if the team that just started the product development is ready to move to fogbugz, then you can always request the team to do so. Learning any bug tracking tool is a matter ...



Only top voted, non community-wiki answers of a minimum length are eligible