Tag Info

Hot answers tagged

10

Being QA Manager with about 3 years of experience, I just give my team mates testing tasks, which are NOT related to software, e.g.: Compose test cases for blender / vacuum cleaner / etc. - any kind of familiar device / equipment. This results in brain refreshing, and for the cost of 2-4 hours I get team "reloaded")) The same is applicable for testing such ...


9

You could setup personas which are designed around real world of users. We have found this quite useful and it really helps to provide a fresh perspective e.g. Today I'm going to be Andy, the super user of the system. Andy is very sharp with numbers and is the user that is responsible for the administration of the system. He enjoys watching sports on ...


7

It's really no different than any other test case. Set up conditions: Check actual result against the expected result So you'll need a list of all the error messages in the system and the conditions that make these errors appear If you want to really test them out then use the FAILURE mnemonic as detailed here.


7

I think the simple answer is, do something else for a while. Our jobs require a lot of repetition, and we automatically develop habits in response to repetition. That behavior is a deeply ingrained survival technique; habits allow us to do things quickly without thinking them through. Sometimes those habits allow us to discover new things, but other times ...


6

If the system needs to scale to many concurrent users or work with lots of data, I would say load testing should be started as early as possible. This way possible problems in the application architecture can be found in a phase where it is still possible to fix them. Couple examples: Let's say that the database schema is such that some queries will be ...


6

As well as "what Joe said, in bulldozer-sized loads", I have a few pointers to add from experience with localization/translation. To test internationalization - which will need to happen first - you'll want something that's really obvious so that in a test environment your team can go through every interaction in the system to check that everything that ...


6

Tracebility matrix is a tool. It doesn't have any inheritent value, but it might be easiest way of mapping certain kind of relations between tests and requirements. As with any other tool, if it seems to work well, use it. If something else fits better, use that. If the tool nearly fits your need, modify it to give what information you need. If testing is ...


6

You could try the 'tours' concept and try out different tours of the software. I'd also disagree somewhat with your premise - the more you use a program the more you notice any slight changes. You also understand more how all the parts interact which in turn gives more ideas. I think at the start you may notice more but they are shallower than ones you find ...


6

allquixotic, How important is it that you get these string correct in all situations? For example, if this is a life-critical application that depends intrinsically on the correctness of your strings (the difference between "Send police to the Town Hall" and "Send fire equipment to the Town Hall" for example), then you must do a deeper dive. Consider ...


5

First, your product probably has some kind of security-related provisions: e.g. authentication, authorization, password recovery, prevent one user from seeing another user's data, and so on. There will be positive and negative test cases for those. Beyond that is the more complicated stuff. There are tools available for scanning websites for security ...


4

Caveat: I've discussed and thought about testing playbooks a little - I'm not convinced that I necessarily have the same interpretation as others, partly because there hasn't been enough discussion of the idea (that I'm aware of, would love references if people have them) for a consensus to develop. This is my best attempt at this point in time, it will ...


4

I'm afraid I don't know the origin of this way of phrasing and I've not seen it before, however I was surprised to see that the answers here consider 'fails if' equivalent to 'passes if', as I quite strongly consider the two to be very different from each-other and also my opinion is that 'fails if' is slightly superior to 'passes if' for manual tests anyway ...


4

As always, it depends. If the system is already sufficiently internationalized, and other localizations have already been performed, then future localizations may be well-defined, documented efforts and their scope may be easily estimated based on past efforts. On the other hand, if the system isn't internationalized at all, then you may need to incur the ...


4

You have been developing this system for 2 years and have never performed any load testing at all? Preparing for expected load is usually part of the design. At this point, you are 2 years in, and may not have any evidence that your design is capable of supporting the required load. You do have performance and load requirements, right? With any ...


4

A few thoughts to add to the excellent suggestions others have made: Yes, full end-to-end load tests should ideally happen after code is stable. These will be used to find bottlenecks in the interfaces between different components of your code. This kind of load test is probably what your QA people are thinking of when you say "load test" - and I'd hazard ...


3

One approach is to actively recruit team members and other stakeholders for testing of the product. I have found that it is useful to try different approaches and use whatever works best with each person, which can include: Paired testing with a code developer (emphasize the thrill of having a function work on the first build :) ) Asking a content ...


3

I have never seen such a matrix and never heard of it before :-(. Your goal: Which requirements is almost never tested, and which is tested extremely often? can be achived by agile/technical means: Using Behavior driven development bdd as automated test for a userstory to verify that it is complete and still working. There are code coverage tools ...


3

A test plan is worth creating if there is something that needs documented testing. It may be frustrating to see a test plan with only a few steps, but if you realize the purpose of the necessity of documentation, it doesn't matter how small the test plan is. You should include whatever it is that needs testing. Whether it's an anticipated UI response to ...


2

The requirements documentation should give a clear description of what is expected. That should always be written in such a way that anyone can tell if the software is successful at meeting that requirement. Given that, I don't think it matters either way which one you choose. I don't think you need to include both, but you do need to define in the test ...


2

It's the matter of conventions in the team, no more. Expected result "test fails if the login form is absent" is identical to "test succeeds if login form is present". The test cases can be incomplete, but it does not matter what convention was used, if tester forgot to add a check for the presence of a search field.


2

I would probably look at STRIDE and allocate a given time to each of the threat areas, the duration that is allocated however, will be determined by the skill and experience of the tester. If there aren't any experienced security testers in the team then you probably wont get any really value from doing this in house, it really is a specialist area. You can ...


2

The above answers are correct, and depending on the importance of the security, you are probably best advised to get some security experts in. Other than that, in order for you to have a go yourself, some useful resources I use to dabble in security testing / ethical hacking are : https://www.owasp.org/index.php/Main_Page http://google-gruyere.appspot.com/ ...


2

I am not a security tester, however, your test planning will vary depending on whether you need to maintain the secure status of the web application, or whether you are doing a one-off "this application is secure" set of tests. In both cases, I do think you need to plan - but for one-off test sets you don't need to plan for repeatability. I'd look at ...


1

I would ask a number of questions before deciding when and what to load test: Where performance problems tend to occur more often in your project: at UI, backend, or integration of UI with backend? What part of your system is more stable? Horizontally, backend services or UI? How stable is the API between frontend and backend? Are there any integration ...


1

Short version Not necessarily. Long version The idea First thing to realize is what open-source means for software: the basic idea is that the source code is available. In more specific terms, someone has decided (for a new project or a running one) to share the code, i.e. every technical detail with the whole world. Furthermore, since there's ...


1

You could also change your testing approach. In my experience, 90% of time spent testing is Exploratory. this tends to get dull and repetitive. What I then started doing was changing my point of view or testing strategy. Try something in the lines of BVA. (Boundary Value Analysis). Obviously certain test strategies wont work on all types of software. It ...


1

Here is a link to a pdf article "Pairwise Testing: A Best Practice That Isn’t" (http://www.testingeducation.org/wtst5/PairwisePNSQC2004.pdf) by Patrick J. Schroeder and James Bach that discusses pairs testing and random testing. In essence, it promotes having multiple techniques in your toolbox when approaching this type of problem. Hope that helps!


1

In an agile environment you can (should) replace these traditional tools by their agile equivalent. Instead of having a matrix in some documented format (eg.: Excel sheet with the requirement and there place of implementation) you can use your tests. For each requirements you are going to have some tests implemented (assuming TDD). These tests then can be ...


1

Welcome to SQA, Teague. Your test plan is part of a feedback loop. You convey something about the project to whoever is testing. They test the project, find some problems, and fail to find others. You incorporate what you observed into how you write your next test plan. It is all about paying attention and being open to changing what you do according to ...


1

There are 2 plugins: Plugin to export requirements from word document to QC Plugin to export requirements from excel document to QC Once you install these in your machine, you will get options to 'export to QC' when you open the respective application. The pre-requisite is to have a properly formatted document (either word or excel). It will contain ...



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