New answers tagged test-design
0
A real life example- Iperf, it is almost an industry standard for measuring network throughput, the common (but not latest) release 1.7.0 is a decade old.
But still when I encountered strange behavior I started digging and found out that Iperf for Windows behaves differently than Iperf for Linux, and this is not even a bug but an OS behavior.
When using ...
4
IMHO, a team lead who is a developer with less knowledge in testing, is the wrong kind of person to be selecting a test tool.
Do you have any QA Professionals on your team - perhaps someone with test tool experience? Or, lacking that do you have anyone on the team who will actually be tasked with using a test tool? I would suggest you turn to them.
If ...
0
Coincidentally, Dilbert provides a nice answer: http://dilbert.com/fast/2013-06-13/
What you need to test depends on the risks you are willing to take.
If you decide to use a new third-party tool, you must decide if it is fit for the task. That "fit" is determined contextually, by the way your system uses the tool, by the availability of support for the ...
2
I'd agree with the other folks here: it looks like you're testing your application's use of the third party tool, and in most cases that should be enough (if you're working somewhere where a mistake would get someone killed, perhaps not so much).
With a tool that interfaces between some form of data and a database, the essentials are testing that when using ...
1
Question: will you be relying on those third party tools for business income?
If so, you probably want to test it.
However, at some point, you have to trust the tools, libraries and more that you use to some extent. They've been tested as well by others. So you don't need to retest them from scratch. However, you should test the code that you use, make ...
1
You have chosen to include the third-party tool in your software. Therefore you are responsible for how it performs in your software. Given that, I'd want to test it.
You may choose to test the third-party tool only as part of testing your software. The danger here is that your tests may not exercise all of the interfaces that your software uses, nor all of ...
4
At some point you have to trust the third-party software you work with. That's not to say the software won't have bugs; of course it will. But you can never test everything. For example, I suspect you do not test the operating system, compilers, text editors, router firmware, printer drivers, and web browsers that you depend upon. (At a previous job, our ...
2
It is always necessary to validate how your tools are working in conjunction with the rest of the application workflow. In your case it sounds like you are already testing the inputs that your are sending the the tool and what you are then receiving from the tool. Beyond that it is a question of where you feel you need or want to spend your time. You ...
4
I'm going to go out on a limb here and say that what you have is an ad-hoc development process rather than an agile one.
Here's where I'd start, assuming that you have the ability to work with the programmers and project/application management on this (you can get a lot of it even if you don't have that ability).
Who - Who is the intended and actual user ...
4
Use cases are a way to translate requirements into something more concrete. If you have use cases, you should test with them. You should test in other ways, too.
How you represent your test cases is up to you. Some considerations for picking a representation might be tool quality and cost, and ease of writing, revising, searching, annotating, and ...
1
In addition to what Kate said, here's one thing I always consider when writing up scenarios:
I am writing them up as an user of the application, so I need to provide all the details that the user would be aware of, and not much more than that. The rest can be handled by the code behind it.
3
Cel,
As always, it depends. If there's a requirement that the link contain a label then obviously the test needs to check that a label exists (whether automated or not).
Here are some of the possible things I'd consider with this scenario:
Is the code dynamically generated or static? For a static "once and done" page, the mark 1 human eyeball might be ...
4
The first two issues that come to mind are scalability and tolerance of faulty data.
Data Science frequently implies large data sets. As a tester, you need a sense for expectations about data set sizes and the corresponding performance. Those metrics need to be put in the context of the computing environment of course; what you can do on a laptop running ...
0
Like the others here, I'm in favor of decoupling and modularizing as much as possible. My preference is to have a set of independent login tests (including checking the message received for invalid login, triggering the security questions if they exist, and so forth). Those would include some valid logins like "Log in as admin", "Log in as guest" and so ...
1
Time and again as a contractor, I've seen large monolithic test structures with code all over the place. Often it's because testers have copied and pasted tests, which then break and need to be fixed in dozens of places, instead of just one.
As such, yes, there's certainly benefit to re-using core functionality, as long as it's not the part you're ...
2
ved, welcome to SQA. You should distinguish between testing the login functionality and merely using the login functionality. End-to-end tests are about ensuring that all the pieces fit together when someone uses the software for a specific task/workflow. If an end-to-end test requires logging in, by all means use the login functionality. However, if you ...
-1
I'll throw out a couple of definitions so I can answer the question with an esoteric and abstract response:
A functional piece of code is any operation that makes changes to a finite system (in other words, a computer.) It is important to realize that there are only a finite number of configurations that can occur on a computer. Obviously, a functional ...
0
For me, the terminology "non-functional" is part of the problem, as it immediately implies a lack of something. Some people use "cross-functional" instead, or terms like "constraints".
What I have found works well is to talk in terms of Features: end-user features and operational features. Focusing on the operational aspects opens up a dialogue with the ...
0
Considering your description, the clarifications can be given as :
Requirement : It is the changing need of the stakeholders which is tried to fulfill by the development team at the time of developing the product
Use case : After the requirements are clear, then the use cases can be designed/decided which will clear the overall flow of the system to ...
1
Even theoretically, unit testing isn't sufficient because it doesn't cover the paths through the system. You can cover every line of code in a system, but not cover every potential way through it.
For instance, can you launch the application? Does it run on all the target operating systems? Does it render correctly? These are all out of the scope of unit ...
3
There are many cases where unit testing as you have described would not be "sufficient".
(And you haven't really defined what you mean by "sufficient" in this case. Good enough to move the code to Production? Good enough to pass it on to QA? Good enough to please your boss? Good enough to feel like you did a good job? Something else?)
In most practical ...
3
Not exactly.
Unit testing only isolates units in isolation. In these tests all dependencies to other units are mocked or stubbed out. So how do you know those units together do what they are supposed to do? Code tends to grow hierarchically in complexity, and with that growth comes more and more units working together, more and more groups of units ...
8
A requirement is typically a general statement, whereas a use case is typically a specific statement implied or derived from the requirement. A requirement may map to multiple use cases. A scenario might be a set of background assumptions that put a use case in context, or it might be grouping of use cases.
Here is a contrived example. The requirement is ...
Top 50 recent answers are included
