Tag Info

New answers tagged

3

You have some choices here. You can go with formal definitions like the ISTQB definition, or you can treat the definitions the way your organization handles them. Software testing is a field where definitions tend to vary depending on the understanding of the team and how they work. That said, in my experience interface testing can be one of two things: ...


0

I take a look into the ISTQB glossary and found this two definitions: interface testing: An integration test type that is concerned with testing the interfaces between components or systems. integration testing: Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also ...


3

The short answer is "No." The slightly longer answer is "The testing needed depends on the application." The things you need to cover in installation testing will vary depending on (not a complete list): Which operating systems the application supports It being web-based, which web servers the application supports (IIS, Apache, etc...) Any other ...


3

There are tools that will generate a set of tests that cover every combination at least once without hitting all possible combinations (these work on the principle that most bugs will be surfaced by exercising pairs of settings). Since the feature hasn't gone live, your business analyst is probably your best reference for the combinations that are most ...


0

Well In our company we follow cmmi level 3 processes. Exploratory is done after complete functional testing which consist of negative and positive testing. When We receive a build of any web based or mobile based application this process we generally use. 1.Smoke testing of the build :- Which consist a short positive flow of application. 2.Functional ...


1

postback (note it is one word) is a term used by ASP and JSF to describe a form which post to the same URL. It is Microsoft's way to pretend that variables on a web page can interact with each other like in event-driven desktop application, but I found it confusing because I know what really happens. SO has great explanation. For you it means that all ...


0

Online tranaction systems in general react to user demand. When the user requests something the request can either be satisfied by the users client device or by that device sending a request (a GET or POST normally) to the centralised servers. A request to the servers will require activity on the network (to get the request to and the answer from the ...


1

Some things I've consider from a strategy point of view in various situations: Could you move to a 'test based on change' approach? Could you monitor the industry for software upgrades (of for example browsers) and new screens (with different dimensions and characteristics) and thus test in response to change as opposed to periodic testing? Clearly you do ...


2

Where I work, there are three web applications that need to be maintained, with a fourth (which is intended to unify all three existing applications) in development. Each has a distinct purpose: Application 1 is an enterprise-level employee and payroll management web application used by both internal payroll specialists and externally by customers. ...


0

So I will try and put an extensive answer to this. The first issue is that this is a text box where an end user can insert data as they please. Boundary Testing Start with boundary testing, by this I mean find from the business what should be allowed and what shouldn't be allowed. Test at the boundaries of what should be allowed and what should not be ...


-2

please check this link from w3schools..... java script validations thanks Prakash Nanda


2

To test mobile applications is very hard. You has so many different devices and operating systems. In some cases you have to test older versions of the application too, to be sure they work with a new backend or something like that. This produce a lot of combinations. No, you can not covering all of these combinations manual, neither with automation. But ...


3

A mixture of both, there is no 'best'.


0

Virtualization software. You can use tools like VMWare to setup virtual machines which you then run from your existing machine. You might be on a Mac, a Linux box or a Windows machine, and from it run WinXP, Win7, Win8, Win XP /w SP1, etc. IIRC even MS has a Virtual Server which you can script to turn machines on and off, which means one script to run all ...


1

Latent bugs are bugs which exist, but have not yet been discovered. They are bugs waiting to be found. also see: http://www.allthingsquality.com/p/testing-terms-glossary.html


0

It should allow some specific special characters which are used in Country/state names. According to me, best option would be providing values in a drop-down, so that user can select desired value from the drop-down and you can put a generic validation message like "Country is required."


0

From some random site: Golden Bug: The bug that is occurred in every instances of the application with severity level high and with high priority.


0

From the dictionary: latent defect n. a hidden flaw, weakness or imperfection in an article which a seller knows about, but the buyer cannot discover by reasonable inspection. Think this term is more used for selling physical items (like houses and cars) and not in software. From some random site: latent bug: The bug that is not identified in ...


0

In my experience, the requirement to collect evidence (like screenshots) of tests being executed is driven by regulations in your industry. I had to collect evidence while testing military avionics (MIL-STD-2167), telecommunications equipment (TL9000), and financial reporting for publicly traded company (Sarbanes-Oxley). When working with software that is ...


0

To document testing scenarios, we use a wiki with text-based steps. Our wiki (FOSWiki) has version control, so you can even see how steps changed over time (and who made changes). Way better than docs on shared drive - hyperlinks make navigation a breeze. And FOSWiki allows to attach images to pages. Linking to other wiki pages with related/similar scenarios ...


0

We record a video of our test after design of what a "good" test case pass looks like and put it in shared storage. After that videos are only kept on fail. This way we can always go back and look at what the original good run looks like.


1

Anecdote: I worked on one project for a national company. Testing was being done and overseen by one of the Big Name consultancies. Their testers were told to take screenshots for every test step. They abandoned this practice as (1) it was taking too much time and test progress was too slow and (2) I was fnding 90%of the defects on the project by doing ...


1

This is definitely not a gender-based thing. I've worked with male testers who were less structured and preferred exploratory testing and females who preferred to create a detailed test plan and work through it. What matters is that enough information about the state of the application in test is communicated to the rest of the team so they can make an ...


3

You may want to take a look at a blog I recently wrote the role of the tester in a team: http://www.softwaretestingclub.com/profiles/blogs/a-conspiracy-of-quality The primary role of a tester is identify risk (e.g. bugs) as early as possible in the application lifecycle and communicate that risk as early as possible. That means that communication (team ...



Top 50 recent answers are included