Tag Info

For me it's a non-functional requirement, even if the key users have some requests regarding the instalation folder location (for better integration with other software packages). UPDATE: The tests for the available features detection are still placed in the functional requirements area, given that: the software can be bin-deployed in some cases, and ...

I would agree with alexandrul's answer, with a few small caveats. First of all, it depends on what the installer does. If it's just a plain normal install, it would fall under non-functional. If there are options in the installer that greatly affect the functionality of the application (ie: add/don't add specific features), I would normally put it in my ...

Generating test data is a difficult problem because if you don't understand the symantics of the data then you are likely to generate test data that will throw false positives in your tests (test failure due to faulty data, not a bug in the product). The approach I have used with great success is parameterized test data generation from equivalent ...

There are two approaches that I have taken to testing a WCF service. I am working under the assumption that you are looking to simulate the configuration both hosting and access that an application would do from a production set up. Hosting it I would set it up in a similar maner to what you are planning to do when deployed. For me this meant deployng it ...

Lyndon makes some good points, it does depend on what your installer does. When I have worked with them in the past, mostly I deal with SaaS and not so much with client apps anymore, but there were a few in my past jobs and we mostly had functional tests for them. The rationale was we were not just dealing with installs, although that was there, but we ...

As I indicated in this reply Accessibility Testing - Should it be considered functional testing or non functional testing? I like the following definitions from http://www.lessons-from-history.com/node/83 "a functional requirement specifies what the system should do" "a non-functional requirement specifies how the system should behave" We have always ...

The answer to this question is obvious: it depends. As an example, the customer complained on that the report generation pages takes a lot of time ~ 4 minutes to generate the report. Our developers were not able to fix the performance without rewriting the legacy code from scratch. So they just added “ajax-like” loading indicator. Well… our customers were ...

If you are curious about the tradeoffs around mock objects, there are entire websites and books devoted to the subject. I will restrict my answer to the specific problem you described. I never replace a real system with a mock system unless the real system does not meet my needs; a mock system requires time to write and maintain, and when a test fails, you ...

I use SOAP UI for this. It automaticaly generates all the functional test cases, based on wsdl definition, it is possible to load test your service, it is free and open source (and there is commercial version), etc. http://www.soapui.org/

When I define my test cases, (Normally in Team Foundation Server) I cross reference them to the requirements. Then, as they pass or fail I use that as a way to determine if a requirement has been delivered or not. Once all the test cases have passed to, it is the testers, not the developers who set the requirement from 'Ready for test' to 'Built'. That is ...

I'm currently trying FlexMonkium and while it seemed promising at first, the fact it only works with Selenium-1 is a kind of a turn off... Here I am stuck again with the "unable to handle file upload dialog" problem that Selenium-2 finally solved. Have to go back to my old Sikuli/AutoIt workarounds. Other than that, can't get it to work well without ...

We tried Flexmonkium and found that it was burdensome to get started and prone to versionitis. We've been dramatically more successful with Flexpilot. We use it with Selenium2 beta3 (WebDriver). The SauceLabs team is helping to move Flexpilot forward, whereas Flexmonkium didn't seem to be getting much contributor love.

I would recommend you taking a look at Jasmine if you like BDD style testing/specifications. Seems to be growing in popularity as well. There are a couple of screencasts on using Jasmine available on the net so you should have no trouble getting started. Check it out at: http://pivotal.github.com/jasmine/

Below option is also one possible soultion Generate client proxy class for the WCF Web service Using VSTT - Data Driven Test Approach for running tests with different test data - http://msdn.microsoft.com/en-us/library/ms182527.aspx For .NET 2.0 testing i have used VSTT for web service testing. It is pretty simple Creating a Data-Driven Web Test against a ...

We categorize things because we believe we need to treat the categories differently. It is hard to express an opinion about why separating functional and non-functional tests is important without knowing how one would use the answer. Important for what purpose? Sometimes people ask such questions in these forums because they did not have an answer in a ...

As with most other tests, let your Requirements drive your testing, without being tool-specific. Do you have Requirements for what your tool-under-test must do? If so use that. Don't let the specifics of how the tool fulfills the Requirement become part of your test cases. For example, if your tool must be able to open an existing HTML file, then don't ...

The best time to start any testing is before any code is received. Performance should be part of the Requirements and Architectural reviews/discussions that hopefully occur before coding begins. That's where you can have the most impact on performance, and can adequately plan for performance testing. In your case, it seems pretty clear that none of the ...

Categories can help. Categories can help with some things. You might use categories to help indicate: Who will write or run the tests. For example, unit tests are generally written by developers (and are sometimes called developer tests). Acceptance tests might be executed by testers or product owners. The characteristics being tested--e.g. functional ...

Why seperating functional/non-functional aspects of a system is important for me as an tester I make such an distinction at the very begining of a project (either during drafting the strategy or implementing it). It helps in making non-functional or 'implicit' (another word for overlooked,forgotten or ignored completely) requirements sufficiently 'explict' ...

There are several reasons to organize related groups tests into different test suites. Purpose - the fundamental purpose of a functional test is different then the purpose of a performance test, or a stress test, etc., and thus provide us with different information about the product being tested. Scheduling - tests organized into suites enable the test ...

Yes, there is a point about separating performance from functional, "If it does not work for one, then it will never scale to many..." The skills needed to implement manual or automated functional tests and performance tests are very different from a tester perspective. Performance testers have a very different view of the system and its architectural ...

I'd see it as more of a tracking issue, I haven't done much non-functional testing (at least I wouldn't call it that) although I could look back and probably say we covered that in some other kind of testing. Mostly when working on a project I look at the Functional Requirements and start basing tasks/tests/checks off that, anything not in the requirements ...

This is a great question, and it's an issue that every product company faces. The answer is very subjective -- it depends on your product, your organization, and your customer base. Although it is subjective, there are trends you should keep in mind when trying to evaluate whether a product meets its functional requirements. As time passes, not only does ...

I don't think there's a single, magic, metric to give you that. You can measure some common metrics and combine them somehow to determine the quality of the software. For example- number of covered requirements like mentioned above (very misleading by itself since we don't know how good the coverage is), number of low-med.-high severity bugs found in this ...

Why do you want to do headless testing? Is it purely due to the environment (such as I want to be able to run some automated tests on a build server that does not have a graphical subsystem)? Regardless of the answer to the above, whatever solution you choose, the final target environment should shape your answer. For example, you could use the HtmlUnit ...