Tag Info

New answers tagged

0

(Writing this answer on behalf of the OP, who answered the question in a comment.) http://stackoverflow.com/questions/528567/how-can-i-simulate-a-disk-full-error-in-a-windows-environment describes multiple methods for filling the entire disk.


0

Consider conditions that cause zero iterations, one iteration, a few iterations, and a very large number of iterations.


0

Developers should find this issue. Tell them to try once again deeply. Also you try to re-generate issue and try to remember that what exactly you have performed previously in testing when that issue is generated. Some time it can be because of database not interacted , Internet goes down suddenly , developer is uploading something and you testing parallel ...


0

Component testing is a method where testing of each component in an application is done separately. Suppose, in an application there are 5 components. Testing of each 5 components separately and efficiently is called as component testing. Let’s take an example to understand it in a better way. Suppose there is an application consisting of three modules ...


5

Here are some ideas (not exhaustive, as is never the case with testing). On a higher level, contribute to establishing a test strategy, master test plans, etc. Static reviews of analysis documents and requirements! This implies finding defects before they're even developed. Testing at its most valuable. You're really challenging the analysts' work in a ...


0

Testing of separate software component is known as component testing. Component testing means testing of single part of software/Website. This can be program module , single function etc. For example if you have website which has 2 page registration process. Now assume that 2nd page data is depend on 1st page data , and if developed has done code for only ...


1

Component testing is testing of specific module or program.It may be done in isolation from rest of the system depending on the life cycle model selected for that particular application. Stub and driver are used for competent testing. These both are consider as component. Best example is given below : Suppose you are testing one application which have 3 ...


2

Kanban is not a software development methodology. It does not prescribe any method of development or testing. You use Kanban for visualizing - and improving - what you are already doing. So, if you are currently a Scrum team, and have specific testing/ test automation practices, you can continue to use the same with Kanban as well. If you are using ...


5

With respect to testing they are the same. Kanban and Scrum are both iterative Agile development models, the goal is to get the most important tasks fully done (including testing) as soon as possible. The product should be potentially shippable at the end of the iteration. The difference is with Scrum the end is a set date, with Kanban it could be anytime ...


1

An area missed in earlier answers is working with your development team. You need to ensure that not only the lead, but each member of the test team has a good relationship with the development tea, counterparts. The developers are your greatest allies. Get the devs to write some more robust unit tests. Explain and have them buy off on your test plans and ...


0

I found this article that describes Selenium architecture and how Selenium works. Quote from the article: WebDriver controls browsers that are running in other processes. Although it's easy to overlook it, this means that every call that is made through its API is an RPC call and therefore the performance of the framework is at the mercy of network ...


1

Yes, it most certainly does. Selenium can only address elements once they're loaded, but that loading (controls, ajax calls, ...) is depending on your connection (and browser). In fact, I had a perfectly working script with nice explicit waits for our test environment. But the execution on the production website went bad in places, because the ajax calls ...


0

You can try from freelancing sites. You will get lot of experienced testers there. You will have diff. testing experts there. You can choose best one according to your need and budget. Utest community is also good solution. That is also collection of good testers.


0

Take a look at a new platform called http://rainforestqa.com. It's a new approach to crowdtesting where you can arrange testers with different web/mobile environments. There is also a number of free test sessions you can execute, so you'll be able to evaluate the tool without needing to pay upfront


1

Why not check us out! We have 17 k beta testers in our community and they together own 470 different devices. You can do both private and public tests and also choose if you would like to pay the testers or if it's a free test. Have a look and see if our platform could work for you. https://betafamily.com/


1

I think that it is important to understand the difference between testing and QA. There is one post you need to read on the topic by Michael Bolton, Testers get out of the QA business. The short version is that testers, who don't change code, are assisting with quality, not assuring it.


2

Applause You could try Applausse the testing services based on their tester network from UTest, I have done some cross-browser and mobile app testing for them. They offer scripted testcases and exploratory sessions where you pay per found issue. Amazone Mechanical Turk With Amazone Mechanical Turk you can define small work loads. Like install and do some ...


1

I don't know of any free ones, but there are a number of services around that do exactly what you're after. Plus, they range from system or system integration testing to beta or user acceptance testing - so it really depends on your requirements. Check out Bug Wolf, 99 tests and Bug Finders to see if they suit your needs. Otherwise, Googling something ...


2

Smoke testing is the term teams I've been on used to describe the initial quick pass on brand new code (or at least a new build) to make sure nothing major is broken in a major way (that will block you from the majority of testing). This is the first step before you get into regression and rigorous new feature testing. You may consider Sanity Testing. ...


0

We are human beings (developers, architects, managers and everyone involved in an IT project) we make mistakes. As PaulDonny mentioned earlier sometimes these mistakes can be costly and catastrophic. By finding these problems (and hopefully fixed by devs) the risk is reduced and the product is made safer to use. We don't add value to the product directly ...



Top 50 recent answers are included