Tag Info

New answers tagged

2

Yes. That situation is defined as Alpha Testing. According to the ISTQB, Alpha Testing is: Alpha Testing: Simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site, but outside the development organization. Alpha testing is often employed for off-the-shelf software as a form of internal ...


1

Lots of terms could describe this, depending on what you want to describe. For example you could describe: the testers, the potential problems they face, the coverage, the oracle(s) they used the activities they perform and/or their testing approach Based on your question it seems like you are trying to describe the testers (or who's doing the ...


2

The activity you are describing what I call "User testing" (assuming that the students are relevant representatives of actual users of the app). Sound to me that the "User testing" is done in a testing phase that I would call "Alpha testing" which would have a milestone at the end, and a fix period, before "Beta testing" starts. Beta testing would be ...


3

Be careful what you measure, because that is what are you going to get. If you ask for 200 purchases, you will not get experience (and testing scope) what you would get by 200 different users making a purchase. You will get one user repeated 200 times. Which is better than nothing but does not tell you how your system will respond to 199 other ways to ...


1

There are different ways to classify testing. If you want to classify it based on the level of testing, I would call it "system testing" or "end-to-end testing", since you are working with a system that is fully integrated already. Since they are working in an environment that is close to the live environment, they are not only making sure that the software ...


0

Typically you bring in real users for a usability test, but if they're looking for bugs, I'd say it's an ad-hoc manual test.


0

QA efforts should be involved from planning to deployment and even post-release bug review. QA engineers should be product experts who can plan before a Dev even touches the keyboard, assist Devs in delivering the right functionality, and give timely feedback by testing the code developed. It is a mistake to keep the tester or QA engineer's involvement at ...


1

I use NUnit which has a bunch of material around the word "Fixture" they have something called TestFixture which is declared at the beginning of your code and is defined as: "This is the attribute that marks a class that contains tests and, optionally, setup or teardown methods."


2

It depends on the context. For instance, in Fitnesse or other BDD frameworks it is the "glue" (an intermediary software layer) that connects test scripts with the system under test (SUT). E.g. translates test commands to SUT API and responses from SUT API back to the test script. My observation is this is also a reason why BDD often fails. Non-technical ...


4

I think the Wikipedia definition of fixture is pretty clear: A test fixture is a fixed state of the software under test used as a baseline for running tests; also known as the test context. It may also refer to the actions performed in order to bring the system into such a state. And In generic xUnit, a test fixture is all the things that ...



Top 50 recent answers are included