Hot answers tagged

30

They cannot be 100% sure of a bug free system. They can increase their confidence that the system is bug-free by use of static analysis and testing. Some people advocate bebugging as a way of estimating how many bugs remain in a system. There are at least two forms of static analysis. If the system goes wrong then it goes wrong. There are assorted methods ...


24

NASA's Software Assurance Technology Center at Goddard once did a test to see how few defects they could get in some code for the shuttle. After a truly rigorous and vastly, vastly expensive process, with multiple levels of review, using very small functions to minimize the risk in each, they managed to get it down to 1 defect per 10,000 lines of code ...


19

All non-trivial software has bugs. Risk is part of life. It is foolhardy to attempt to remove all possible risk, because in the process, you introduce the risk that you will accomplish nothing. Even if your algorithm and your implementation are perfect, your software does not live in a vaccuum: it depends on compilers, interpreters, libraries, operating ...


8

Things are expected to slip through if you are just given a once through correct? Im not talking about a lot of major stuff. But little things (especially if it's a large website). How do I not beat myself up over this? Yes. There are innumerable levels of quality and bugs will slip through at each of them. Consider these levels: Is it possible to ...


6

Requirement Traceability matrix maps the user requirements with the test cases. In simple words, the matrix helps in determining if all the requirements have been covered(i.e there are test cases which can be traced back to the requirements). There are 3 types of RTM: 1. Forward:Requirements->Test Cases 2. Backward: Test Cases->Requirements 3. ...


5

Although, this question is too broad to answer but in short I can say 'It depends upon number of factor which tool you want to use'. Project/Organization budget Scope of Automation Skillset available with team Complexity/functionalities of automation Reporting Test case management Tool support, etc. Don't just compare the tools theoretically, use them ...


5

Two methods in Scenario Testing System Scenario Use-case and role-based scenarios Test Scenario steps for any application In system scenario, you can use step by step module wise system scenario. In that using module & sub module functionality. example for system scenario Application: Test Scenario 1: Check the Login Functionality Test ...


5

Software isn't fault free. When dealing with mission critical software, sure, you need to invest a lot more in quality assurance, and you need the best developers you can get, and you need to get them all the fancy tools and use them (including picking the best language for the job). With all that, you're still going to get bugs. The main solution is ...


5

I stumbled upon some black box techniques, but I don't really get how it works. I found sources saying that black box techniques are techniques in which you input something in a program and check if the output matches with the wanted result, if it doesn't, there's an error somewhere. Let's help with the terminology first: Black Box Testing typically ...


4

Yes, you can do that. For this you need to save your common/shared test steps in a new test case and then change it to a template using 'Mark as Template Test'. Then where ever you need these shared steps, open that test case and in the test step section of that case select the option 'Call to Test' and then select the shared test case template which you ...


4

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


4

Option (B) will be correct answer. (B) 0, 1, capacity, capacity plus 1 Why? Let first understand BVA.. Boundary value analysis (BVA) is defined in Wikipedia as a software testing technique in which tests are designed to include representatives of boundary values in a range. In your example, Seat numbers can range from 1 to capacity. So these will ...


4

I shared this more than once 37 Sources for Test Ideas Become a Skeptic, it will change your view of the product but also of life


4

As Helping Hands correctly said- Agile doesn't dictates the way or the format in which you write or arrange test cases. But for your greater good, you should have separate excel sheets for different modules (considering the application isn't a huge one with lots of functionality). It would be a lot easier to manage and execute test cases (manually), ...


4

TextBox: Verify name is mandatory or not Enter the value as blank spaces on mandatory fields and click on Save button Enter the value as Special Character & Numbers on mandatory field and click on Save button (a. 12345, b. /--+-, c. 12354/--+-) Check Data type(s) for required field Enter value as "a to Z" and check the character length and click on ...


4

Is there any general approach or methodology to create complex user scenarios for any application or is it completely context-driven. In the BBST Test Design slides Cem Kaner describes a scenario as "a hypothetical story about the software. A scenario test is a test based on a scenario." He then says a good scenario test has 5 characteristics: The ...


4

Yes and you're definitely ahead of the crowd already with the plan you've laid out. Additional considerations: In addition to using a Page Object Model, consider a central place for hard coded values (simple methods that return a string in some cases). So the identifiers for the css locator for last_name are in one place (along with other css element ...


4

Been in that situation, and far more than I'd like. While we'd like customers to provide complete and iron-clad requirements, it never (and I do mean never) happens. Well, unless you're shooting people into space. I hear they do a pretty thorough job. For the rest of us, it's generally a continuum. The bits of this you don't have as far as requirements ...


3

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


3

We are currently in a similar situation, except not with Selenium, but with CodedUI. I think for the concept the technology does not really matter. We have defined a critical path with functional locations that are most critical to our application. This because we have nearly no automated test coverage and want to start with the most important parts first, ...


3

B. 0, 1, capacity, capacity plus 1 is the correct answer. In BVA we consider valid as well as invalid values. The minimum number of seats that a person can book is 1 hence we will try to book something which is less than the minimum number and more than the maximum number. 0 is less than minimum number -Invalid partition 1 is a valid value so it is a valid ...


3

Here's how I look at test scenarios and test cases. Test Case - small, self-contained, tests precisely one thing (the thing can be a system action such as "log on with correct credentials" and may or may not have a number of implicit requirements, prerequisites, or steps) Test Scenario - sequence of related test cases performing an end-to-end test of a ...


3

Research and Analyze. Period I think these two tools are enough for a tester to generate creative ideas. And I would like to give you a simple example. Talking of your question, if you would have researched the SQA website well enough, you'd have known that the question put forward by you have been asked multiple times- here and here. If you would have ...


3

This question has been asked many times before on this forum. So you should try to research a bit before adding this question. Take a look at Here where there is a list of good thinking tools and techniques mentioned for improving your practical thinking ability. You can start by reading the number of books mentioned here You can also follow many of the ...


3

Radio Button All options are displayed All options are enabled Multiple selection is not allowed. If multiple selection is allowed, check if you are able to achieve it. If radio button is a necessary field, check if not selecting it raises an error message If any event is associated with radio button, check if that's happening correctly. Click on radio ...


3

White-box Testing White box testing is a testing technique, that examines the program structure and derives test data from the program logic/code. The other names of glass box testing are clear box testing, open box testing, logic driven testing or path driven testing or structural testing. White-box Testing related requirement UNDERSTAND THE SOURCE CODE ...


3

Everybody keeps repeating that all non-trivial programs have bugs. That just shows how far from mature is software engineering as a field of study, and how big gap there is between computer science (solving theoretical problems right way) and software engineering (solving practical problems in a practical way). There is whole body of research on formal ...


3

(Edit to add answer here instead of just linking to a blog entry, thanks for the feedback on my original) Here are some ideas for a test plan for your complier. Many of these ideas were derived from a blog about how Microsoft tests their C++ complier. Functional Tests: In short, you should write many programs in your DSL and test the resulting programs. ...


3

I assume you consider a technique to be proven if it has been shown to find bugs. I also assume you are interested in messaging in the backend system sense, not in the instant messaging sense. A network partition test is a test in which network connections between nodes in a distributed system are temporarily severed. Aphyr has a series of blog posts ...


2

+1 for it depends If the upload operation in your example can only be done through the mentioned failed menu than it is difficult to not fail it. OTOH maybe you are part of the "upload team" and all you want to do is verify this small operation and not end to end integration, so failing the test is out of the question Another approach (I use it with ...



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