Tag Info

New answers tagged

0

As an example, suppose we have a feature to be tested. With this feature we have a test case like: 'Do localization testing before marking the feature as done'. Now during implementation, we realize that one or more specifications have changed and because of this, no new strings are being added to this feature. So our test case for localization as written ...


2

No one here can definitively answer an ambiguous question like this. Go ask the person who wrote the test cases, or the test manager, or someone else on the team who has already figured out the answer.


1

Answer is "when its not feasible/possible to perm a test" It is used for "multi-environment" test-cases and/or if it is some type of generic test-cases script My real example, it would been need to test feature of upload several files same time. But old versions of IE doesn't support possibility to select several files in dialog - so it is "No apply" here, ...


0

The cause of this issue Overall, the cause of this issue is poor multi-threading programming. What is happening is there is likely a static method that is being shared that tracks the user's account. If 2 users access a page at the same time, it is using the second user's log-in in the static method and returning for the first user the 2nd user's ...


0

I would recommend using Apache JMeter to simulate increasing number of users. It can look pretty much a real browser (apart from lack of JavaScript support), however supported browser's functionality include: Headers via HTTP Header Manager Cookies via HTTP Cookie Manager Cache via HTTP Cache Manager There are also several JMeter Assertions available so ...


1

Some of Major areas covered are Network latency, Response time (Load & Performance) Scale out on demand Security Testing CDN aspects if available


0

I would try to reproduce the issue with the open-source FunkLoad, see the getting started tutorial. FunkLoad emulates the browser (including cookies): Truly emulates a web browser (single-threaded) using an enhanced Richard Jones’ webunit: basic authentication support cookies support It can scale up to hundreds of simultaneous ...


0

Functional testing for admin user which he controls private cloud. Security testing for admin. Functional testing for user which permission provided by admin. Load testing for data store. Security testing for normal user.


0

Parking Calculator as said above is an excellent website. Apart from that below are few websites (some belonging to automation tools). I believe these can be used for dummy testing: There is a book named “The Web Testing Handbook” by Steven Splaine and it has a case study. B&D is a fictitious online brokerage firm created with the specific purpose of ...


0

Smoke testing is normal health check up of a build before starting the in-depth testing. Sanity testing is to verify whether requirements are met or not, checking all features breadth-first. Depth of sanity testing is more than smoke testing. Sanity testing helps in identifying whether the test case results are consistent or not. Some people consider both ...


0

For Android & iOS : You can refer this blog, it contains practical result to your queries


0

I have till date only worked with Web Applications and there is this idea/method I use which I think can be generalized: At some point during the testing I envision myself as a little kid. Kids are impatient, greedy and want everything all at once(this is not a judgement. I have a wonderful little nephew whom I love to pieces). I try to do the same. I go ...


0

Collect all info about your work before starting it Assign two roles to yourself first as a one who is inspecting the work , other as the one who is doing the work Keep on asking the questions to yourself and try to use your past experiences Try to concentrate on the work by


0

I believe that for finding good or more bugs you: need to understand the functionality in-depth, in a way you should be aware of all the ins and outs of the application. domain knowledge is also of utmost importance. try attacking the application with incorrect data. stress test the application. run negative tests. For more examples you can go through ...


1

Christina This question comes up from time to time. You may find the answers given in this post of tremendous help. What are key properties of a great QA team member? It will be hard for anyone to suggest programs to you unless we know more of your testing environment. Although it may change in the future, we use no automation on our testing team. If I ...


-1

You could also look at: How the application will behave if network speed is low How the application gives output if multiple application are using the same networks


1

The terms can be confusing because of how they are normally used in the software business, where "QA" is typically synonymous with testing. Quality control is a statistical process. In manufacturing, quality control might mean testing samples of the product as they come off the assembly line. Software is not a manufacturing process, and quality control ...


1

"A" stands for "Assistance". QA cannot "assure" quality - quality has to be build in into product by developers using processes, and QA provides info to management how these processes work, how improvements can be made, and what is quality status. To release or not to release (with currently known detected bugs, and possible unknown bugs) is business ...


0

There are no separate stage for QA. It is an activity of process and product quality improvement and QC it is a stage of checking and reporting about current quality level.


1

What do you need to be a great QA Analyst? There is a lot of answers to this portion of the question. The main things I think would be: Know yourself Know your limitations and strengths. I am weak with UIs so whenever I am tasked with a piece that uses UIs, I typically will ask for assistance and get a 2nd party to verify that I did not miss ...


2

I'd suggest starting with looking at the answers to these questions: How to become a more Creative Software Tester? How can a Software Tester use "Out of the Box" thinking approach to find more bugs? There are a lot of useful suggestions there. Some other things that can help: Practice pattern recognition: Take a large data dump or log ...


0

The main motive of the QA person should be "How to break into the system". This statement keeps on driving me and helps in delivering the application as per requirement specifications.


4

The one thing I think it's necessary to know: The essence of the job is to provide decision makers with accurate, relevant, timely information about the system, to help them make better decisions. Of course, you will also need to learn zillions of strategies and techniques for providing that information. But the key is to remember the point of what you do: ...


5

One very helpful trait would be ability ("knack") to search available information and being able to find what you need. If you did simple search in QA (I used search string "how to start qa") you would find many answers, like: How to become a good QA employee How can I transition into getting into QA? What does a Sofware QA Person Need to Know to Perform ...


1

I've done it and basically I find these sorts of interviews come down to two main points. How well do you understand Test Plans, Strategies and documentation? Can you break down a project so that it communicates what you intend to do in a document that is handed to either someone outside your group or someone unfamiliar with your task. Can you communicate ...


0

Just behave like a teacher and student.Ask Question to yoursely and try to answer it. Always be alert and make an imaginary view of the things.Be creative...


0

Testing in every domain is different because any testing requires domain-specific knowledge. During my career, i worked in such different domains like: mortgage loan servicing (non-performing = overdue loans, which require lost of complicated handling, like knowledge that in West Virginia there are differences in foreclosure procedures per county). We had ...


1

As Chris has said, domain experience means that - in theory - a candidate won't need the lengthy domain learning time that's needed. For instance, I'm currently working in payroll and HR management. To be able to effectively test my employer's software, I needed to learn how payroll and HR management works, and the US regulations that the company needs to ...


0

Other comments have covered the screenshot taking, so I address the third questions: Encountered disadvantages in using mindmaps for test analysis. So: Sometimes projects are long and complex, and on those the state of testing is hard or next to impossible to interpret from mindmaps. Still, capturing screenshots is overkill in most of the situations. The ...


0

Everything we do as testers requires some trade off between time (planning and executing) and achieving our testing mission. Taking screen shots to reference later or to have proof of coverage is fine as long as you balance that with time to achieve your mission (including adequately testing the system). Realistically this means if we want to record our ...


0

Any time someone considers a career change it can be difficult and stressful as you go from an area of comfort to an area of relative unknowns. The difficult thing with learning about testing is there are so many people out there with misconceptions about what we do that it can be hard for someone new to get and stay on the "right path". I'd suggest finding ...


2

Companies like it when new potential employees have similar experience because in theory it gives them some familiarity with the industry, terminology, rules and regulations, common technologies and maybe even with theirs or similar products (as a basis for comparison). In theory it also makes it easier (or more familiar) for recruiters and managers to ...


2

Smoke testing is less about QA than about saving time. The term comes from the electronics business: you plug your new device into a power outlet and watch whether it starts to smoke. If it does, there is no point in testing any further. The analogy for software could be as simple as checking whether the program crashes as soon as you start it. More ...


1

It actually depends. At first, testing requires other skills than programming. If you will became test engineer with programming experience you would be able to automate more efficient and find accidental regressions better. less pressure on work. and again, softare testing could be very responsible job and you can get much pressure. i have java ...


0

Below link have lots of device available so you can test with more flexibility : http://emulator.mobilewebsitesubmit.com/


1

Welcome to community! I believe that manual testing should be always important "till the end of the world". But I also deeply believe that software tester should be familiar with some programming language and script language. But, again, if you are really great manual software tester you will be always valuable employee. Good luck.


1

You can switch your career from java developer to testing field. Mainly software testing includes : Manual testing Automation testing At first, you should learn what is software testing. What is software testing: Test plan, test cases, test scenarios creation Test design techniques Bug reports using tool like mantis , BT tracker , Jira Software ...



Top 50 recent answers are included