Tag Info

New answers tagged

0

Exploratory Testing is a testing approach that allows you to apply your ability and skill as a tester in a powerful way.Testers have to understand the application first by exploring the application, finding out about the software. Exploratory testing is a simultaneous process of test design and test execution all done at the same time. The focus of ...


0

Monkey testing has it's perks, particularly if a test is being recorded so that when an exception is generated there's an understanding of what caused the exception. Ad hoc testing is useful for testing a resolution to a specific bug (retesting). Scripted testing is great for regression situations where you need to exercise all of, or the bulk of, ...


0

I am working as QA and also to write a test cases of mobile application and web application. In Both Application required in writing the test cases are : Test case id Test case(unit to test) Preconditions Input test data Priority Steps to be executed Expected result Actual result Pass/Fail Comments and for more information see below of reference link ...


0

In non-technical English, "ad hoc" means "something done for a particular purpose, as and when necessary". The literal translation of the Latin phrase is "to this". http://www.oxforddictionaries.com/definition/english/ad-hoc "Ad hoc testing" would be something done as a "one-off," for example devising tests to diagnose the cause of a particular problem, as ...


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 ...


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 ...


0

If the QA Lead will have responsibility for a number of test engineers, I would ask questions around coaching and how this person would ensure that the test engineers are doing a great job and are developing in their roles.


0

I read this one online and really liked it: 7) To what extent should developers do their own testing or do you believe testing is the responsibility of the QA team? from here Your first focus is on whether they have the technical skills to perform the job in general. Your second focus should be on whether they'd be a good fit at your specific ...


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, ...


0

Testing in debug mode will only let you reliably test truly surface stuff, like UIs. There's so much extra stuff loaded "under the hood" - like stack frame protection - when running in debug, that you're end-stage-loading the testers finding nasty stuff like memory allocation and stack problems (depending on what language you're using). Any formal testing ...


0

Testern should not test in debug mode, but only devs should do this in their development tests. A good testing strategrie provides the following enviroments: Developement enviroment for development tests (with debugmode switchable by the devs for on/off Integration eviroment for the QA to test the software under real conditions - this especially means ...


0

Below are the components of a test plan, which should be included. 1. Summary 1.1. Introduction - Provide an overview of this document in this section 1.2. Scope of testing - The scope of testing needs to be clearly defined. The plan should define items / features that are in scope or out of scope for the testing phase. - 1.2.1. **Features To be tested** ...


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 ...


0

My favorite is this one: I'll give you a software to test next Monday. You will have to finish test activities to release it on Friday I'll ask you next Wednesday how is your progress. How would you manage to give me appropriate information? I expect the person plan the activities with a test inventory, defines a coverage and provide metrics, a ...


0

Firefox has a rest posting addin. You can also use Excel VBA httppost capability.


0

In Microsoft Test Manager, in the Testing Center view, select Test, then Analyze Test Runs. You'll get the test run history for all runs of your current test plan.


0

I feel very happy to answer this question as I faced same situation recently. I worked 3 year as QA engineer and then I got an opportunity to start "Process Implementation" in an organization, as they wanted to be Agile. What I Did - I used TFS (previously they were using Mantis). I target only one team, (company has 9 product and their teams). I ...


0

You want to test the web service manually, and unfortunately it is only possible with some interface. Web services are not visible and only applications can communicate with this. So my suggestion is test the Applications that are using the web services. Doing so you will be indirectly test the web services.


0

As already mentioned here, there are lot of open source tools like SOAP UI etc.. and plugins like POSTMAN, RESTCLIENT etc... which can be used to send GET/POST request and check response. Other than these, if you are comfortable using java, you can write a simple code using httpclient library to send GET/POST request and validate the response. At the same ...


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


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.


0

Just a little thing to contribute. I think that there are some questions to answer in order to decide: Do you need integrated metrics or will you have separated metrics for each team? The impact on the decision is direct. I mean, if you will make a team learn and change the tool they are used to use, it has to add value to the organization because it will ...


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 ...


0

I think you should follow tracability matrix and always add new requirements/Features to same matrix so old will be there as record and also you will be able to track new. As a tool Excel is fine as start level but I would suggest to use TFS to log all old and coming requirements. It will allow you to maintain all requirements/Features history in very good ...


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 ...


0

You should use the same tool, as it will make your work easier, because in that case you will have to track only 1 tracker, but as far as processes are concerned, I doubt that you will not be able to follow the same process as your both project are based on different SDLC (Scrum and Waterfall, as mentioned by you). So if SDLC is different whole game play is ...


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 ...


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

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, ...


0

Bug Tracker lets you stay on top of everything to do with your project or tasks, but sometimes your stories need a little something extra.Fortunately when some of our customers feel that way, they share the results. Here’s a roundup of recent test related Third Party Tools to help you make the most of your bugs in Tracker.



Top 50 recent answers are included