Tag Info

New answers tagged

0

The goal of testing is to learn about a product. Of course it can be by finding bugs, but it can also be much more than only that. You may find that a feature is missing than a part of your users will need, that something is confusing, that your product is not usable if user have color blindness. You will discover if your product is fun or boring to use... ...


0

when you need to test ur site for mobile devices, best and economic thing is user agent. Just go to google.com, enable site emulation by right click on site and go to inspect element and go to Show Drawer (icon something like >= ) then go to Emulation and then to device, now select any kind of device you want to check.


15

I work as a Manual tester on a big project. My project follows Agile methodology. I test a Web-based application. I sometimes ask my self , that am i giving any value to the stakeholders? So, the value that you are giving to stakeholders is the reduction in the amount of defects that go to production. The cost of fixing a defect drastically increases ...


3

Tester is just a label on an employee. Testing provides value. It is virtually impossible to write bug-free software, and so software that has not been tested is virtually guaranteed to be buggy. Someone needs to test it. Who tests depends on the circumstances. Some people are good at testing, and some are not. You probably want the person who tests to ...


0

I am working for a top large enterprise software company. I've worked for internet company and consumer product companies. Assume you mean taking screenshot for manual test execution. I never heard that screenshot is taken even no bug is found. If the intention is to simply prove the test is executed, you team got a trust and management issue, address it ...


0

My recommendation is a core set of automated regression testing should be part of the build process, if you don't have a CI pipeline. Or at least it is executed on regular basis based on the build cycle and the cost of execution and result investigation. This core set of regression test should be executed and maintained through the whole development cycles. ...


0

Best approach would be the understand the requirement or the situation and test accordingly.


2

Check out the test heuristics cheat sheet: http://testobsessed.com/wp-content/uploads/2011/04/testheuristicscheatsheetv1.pdf This will give you some ideas of what types of things to look for when testing a given type of system. For example, when testing something with an input, do boundary testing (test the limits: what happens when you input nothing? what ...


0

Defect reporting tools are going to vary at each company. For example; some places use HP's QLM, some places use Target Process, some places just use Word/Excel. (I'm not associated with any of these companies but have used them at clients in the past!) As far as the content goes... you've kind of answered your own question. The report needs to be clear, ...


0

Since I can't add comments yet, I'll start with an answer: Begin with the simplest case scenario. You said you have 5 individual modules. What's the minimum you can do in module 1 to provide the output to module 2, etc. Map that out on a piece of paper with each module being a square and an arrow going from one module to the next. That way if they can ...


0

The short answer: Imagine you're trying to guide someone that's blindfolded through an obstacle course. They'll need to know where they are, details about how to move, and information about what to expect at each step. Bug reports are similar; you need to use words, pictures, and video to accurately guide them through what you were doing, what you ...


0

As a couple have already mentioned (thank you both) - uTest has a lot of resources for testers of various skills. **Disclaimer, I work at uTest/Applause. Gigs, You might find value and enjoyment in some of the courses we've setup: http://university.utest.com/ We have a lot of learning and sandbox opportunities so you can play/break/learn in a controlled ...


1

There is no possible single and perfect answer to your question. No matter how big or small the project you will have to understand its requirements and architecture. Now you say you have to do white box testing so I believe you will have to be involved in code review and optimization. For this you will require to go through the code, the whole of it. As ...


0

Generic guidelines you can find in a similar question Best guidelines for bug reporting?. If you're looking for examples of bug reports, I would browse through bug reports for open sources and publicly available projects. It actually makes no sense to link such places. Rather, you need to find an application or programming library that you use or are ...


4

There's no single answer for this - a lot depends on how your organization prefers to manage testing. Here's how I'd approach a situation like this (using a manual version of the answer I gave here): Who - who is the application intended for? Knowing who the users are tells you a lot about how they're likely to want to use the software and what parts of ...


1

The answer to this is simple and complex. You start by reviewing the requirement and writing what is called a Test Strategy and Impact Analysis. This is a general overview of the software, how it operates, the different functionality and, typically, I will assign a value to the 'importance' of each functionality. By doing this you will naturally start to ...


0

Mandatory fields marked with asterisks Proper validation testing (client side and server side validations) Mandatory fields must not be entered empty Maximum and minimum character limit for each field Email address field must properly validated (with regex) Mobile number format must be proper Postal code validation Proper database testing all fields must be ...


1

What you should do is ask your customers what they want. In this case ask your developers what kind of information do they like to receive about any bug and in what format. Usually prepare a proper story of what you did to generate a specific bug and why exactly do you think it is a bug? What will happen if you don't fix this bug? Maybe make a video ...


0

you should have a look @ http://www.softwaretestinghelp.com or specifically http://www.softwaretestinghelp.com/how-to-write-good-bug-report/ this will help you.


0

First of all: Something like one perfect bug report for all projects and types of applications does not exist. But you can talk with the developers and stakeholders of the project and discuss improvements of the bug reports you create. After a while you will have reports who everyone like. Here is an example how I write a bug report: Preconditions: The ...


0

Roughly I will check following things: 1. Verify each and every field for number of characters, is mandatory, any restrictions (like only numbers allowed, only chars allowed etc), validations for email address 2. Is it possible to submit without entering mandatory fields? 3. Is it possible to use same email ID twice? 4. What happens on cancel button? 5. ...


1

I will open Xmind and prepare a mind map of the test ideas which i will decide depending on the priorities, risks, time availability and cost. Then I will get feedback by someone and see if I have missed out anything...


1

We use Usersnap on one of our projects that handles about half of what you asked for: It records bugs directly to a bug database (or where-ever you point it to) Automatically takes a screenshot of page where bug is found It doesn't save the HTML of the page but it does take record some of the reporters info like: IP address Email address Screen ...


1

Saucelabs and Browserstack are great emulators for testing mobile devices. These services provide a wide variety of platforms that can be used for manual and automated testing. Browser development tools can also provide a way to emulate mobile devices. This will give you a good idea of how the environment will display and function with your site. With that ...


0

From my experience, exploratory testing is good to do to understand the application very well. But it does not guarantee the full test pass as we won't track of the test results here. Have a functional testing to cover the high priority scenarios then go to Exploratory testing. High level planning is better than zero planning.


0

Yes we too do exploratory it's very important to perform due to which we encounter the issues, which may occur while a new user is using the application. Definitely it is performed in the last phase but it's not ignored at all.


0

Its a yes,Automating your manual test cases gives you good automated results but i am here speaking with reference "CONTIZEE" tool which i used in automating test cases where zero coding knowledge is needed and time saving. Executing a simple test case and a complicated test case needs just needs same effort in this tool.


-1

There is another online tool https://saucelabs.com/. Check this out Thanks


4

One of the options is as you have already tried - browserstack. Then you can install android SDK on your machine. It provides an emulator for various screen sizes and android os. For iOS you can try the xcode. I haven't used it personally but it is somewhat like the android sdk but for iOS. You will need Mac OS and iTunes store to install it. BUT No ...


0

A very basic explanation Website is just a web page where most of the time testing will be of broken links and broken images and more if SEO is being processed on/for that website Web application is a application where there has to be more work from the testing point of view for example applying various types of testing


0

I would say the website is what the user sees and can interact with in the browser. The web application is the thing that handles those interactions and tells the browser what to display. The user doesn't interact with the application directly, only with the website.


0

Without talking to you directly I don't know what exactly what you mean when you say "exploratory testing". When I say exploratory testing I mean: an approach to software testing that can be described as simultaneous learning, test design and test execution. Exploratory testing is contrasted with scripted testing but they are both part of the same ...


0

There are a few possibilities, and the most suitable depends mostly on Does the test designer know for sure he will also test the case Are there some sort of criterias existing stating what is the correct output So if it is possible that someone else is going to test the case, a bit more effort should be given to describe the desired test. On this case ...


3

The difference is in an individual's perception. It all depends on what you think. Many would say that Facebook is a web application, whereas others would say it is a website. For example services like the ATM software, payment gateway, email service can all be thought of a web application. But if you really get into the depth you will see that they have ...


0

A few ideas come to mind: If this is a webapp, the data may be passed as JSON to a javascript library, so you could verify the data in addition to the visual output. If it's using a well known graph/chart library, this may be sufficient, otherwise you're going to be testing the library and not your application. Obviously, still spot-check the graphs, but ...


1

what is the difference between the Website and Web application? From a QA point of view, there is no difference. Some application development tools/environments have these as different choices, depending on the tasks involved in the project (see: http://msdn.microsoft.com/en-us/library/dd547590(v=vs.110).aspx)



Top 50 recent answers are included