Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
I am using TestNG and Selenium webdriver via Java.
Is there any tool that can help generate detailed test results, for example, suppose I have a test case that fails more often than not, is there a tool that can statistically report those test cases that fail more often than the others like in a graph, or pie chart, etc?
XL Testview
Have a look at XL Testview from XebiaLabs.
Test analytics and decision support that spans testing tools
See all your test results in one single dashboard
Analyze test results across multiple test tools
Track release metrics and quality trends over time
Use real-time quality data to make the best go/no-go release decisions
I havent used it, but seems to track results over time. Seems pretty interesting.
Test Result Analyzer
Or have a look a the Test Result Analyzer plugin for Jenkins.
Many of us have a requirement of knowing the execution status of a
test package , test class or test-method across multiple builds. This
plugin is an implementation of the said requirement and shows a table
containing the executions status of a package,class or a test-method
across builds.
This plugin supports jUnit and TestNG results sets. Looks like the minimum you want and it is free. :)
Tesults - it handles all this including identifying recurring / continuing fails. In general it's a great central place for a team to view and assign failing tests. Please be aware that I work at Tesults.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
How to decide which type of testing(Manual or automation) required for a project or application to test?
What are the parameters we have to consider to select which type of testing(Manual or automation) to test very new application?
It depends on :-
Size of the project- If the project is large and consist of so many functionalities then automation testing is suggested
How many times you want to test a particular feature- If the requirement is to test regularly then automation test is best
Font size and image- This can not be tested through any automation tool so to test this, one should need to do manual testing
To find bugs- If one needs to find a lot of bugs, Manual testing is suggested.
You shouldn't have to choose between automation testing and manual testing the way you're asking. The way you're asking it gives me the feeling that the product is already waiting to be tested. In this case you would need to resort to manual testing.
Ideally you would want to have both and even more of automation. Some of the questions that you need to ask are:
Is this a new project or an existing one? If it's a new project then it's easier to plan for automation from the start. You could start implementing automation tests from the start. If it's an existing project then you'll need time to set up automation + write scripts etc. Then you have to resort to manual testing initially.
Is there any existing team? If yes, then what are they doing. You need to continue the process instead of suddenly disrupting it for anyone.
How much resources (money+people) do you have? Do you have manual testing resources? Are they busy or do they have bandwidth? How many automation test resources do you have?
What kind of project is it? Who does it go to? Does it have human lives depending upon it? Does it need a legal certificate of some kind for being tested?
There's just too many questions based on how your question is currently stated. I hope that this answers your question when we consider it generally. But if you're looking for a particular answer then please consider adding more context.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
Which tool would you say have the fastest learning-curve for "ordinary people" (ie, people whose experience with computers is basically using Faceboook) to be able to write "web tests" (for instance, "access this site, type [X] on this input field, press button, wait 5 seconds, check if the response contains 'OK'").
I'm looking for something that could be teachable in 5-10 hours. I don't care if it results in a stable and very reliable test. This is just to be an alternative for a "monkey tester" while integration tests aren't developed.
The simplest idea I can think is a macro-recorder (recommending the tester to wait a longer time for things that may take longer) and taking a screenshot in the end (the tester would select parts of the image that are important).
Is there anything better than that (or at least that)?
Thanks
With 5-10 hours learning Selenium IDE for basics tests should be more then enough.
It's free
Huge userbase, lots of learning materials and ready to use examples
No installation needed, just add-on to firefox (or other browsers as well)
A little familiarity with html and javascript enables you to write rather complex tests for your web application
If for some reasons Selenium IDE is not an option for you you might check products like e.g. Ghost inspector or Visual Studio Test Manager.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I know Selenium IDE should be needed to record/playback a test. What are the other things in selenium i need, to automate test cases. I am not sure about anything other that recording and playing back. How does this selenium actually works. Do i need to code any programs like developing? or only recording the test will be enough? Share you knowledge about Selenium test.
Where can i get best tutorial for Selenium?
Do i need to code any programs like developing? or only recording the
test will be enough?
This largely depends on what you require your tests to do. If you only need to record a very straightforward set of tests, using the Selenium IDE and recording tests will probably be sufficient. If you are trying to make a robust and extensible test suite, with varied input and/or varied test conditions, you will probably need to do some development to fully tap into the power of Selenium.
The best resources that I know of are the official Selenium documentation, which is well-written and even comes with a bunch of pictures to help walk you through starting with Selenium. For more detailed or technical questions, I would refer to the Selenium google group, which is pretty active.
I recommend these high rating Selenium video tutorial (duration : 2.5 hours in 3 parts) :
http://www.youtube.com/watch?v=3BeK5aH2y3Q
http://www.youtube.com/watch?v=jWDGM4eZqVw
http://www.youtube.com/watch?v=7dC7eiDqytc
Although its title is Selenium + JUnit, but actually it is all about Selenium IDE
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Can anyone recommend a good Selenium Grid "host" for running tests? Instead of having to set up my own network of testing machines?
I'm personally partial to Sauce Labs. For me, the recorded screencasts of your tests is really the key feature. Essentially you just point your existing tests at a sauce server instead of your localhost and you're good to go. One slight drawback is that they don't have Mac instances available for test. They offer a free trial to get you started.
The major thing sauce doesn't handle well is load/performance testing. For that, look at BrowserMob. Essentially, you're driving load tests with real browsers using selenium scripts.
I've heard good things about PushToTest but never used them.
One thing to note is that these are all Selenium 1.x providers. Selenium 2 doesn't have a grid yet, but that should be coming soon.
Selenium Grid2 is now available.
I've been looking at services, and the two most comparable for grid testing look to be sauce labs as mentioned above, and also browserstack which offers a cheaper "unlimited" package I believe. It has 10 parallel users, which I'm not certain if those compare to VMs that sauce labs uses in the same way. This project requires testing over a full suite of browser variations, so the parallel and unlimited aspects are key factors for us.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 4 years ago.
Improve this question
We have an automated regression test setup for Functional tests and
are interested in measuring the test coverage/code coverage for our
project which is based on Linux.
I would like to know if there are any tools which can be used for test
coverage/code coverage measurement without instrumenting the code.
Please suggest any tool or method that can do this.
I am aware that instrumentation provides the best method to measure
the code coverage, but it would suffice for us if the tool can just
measure the functions that were executed for the test coverage
measurement.
Thanks and Regards,
Prashnk
There's only three ways to collect test coverage data:
Instrument the program, and let the instrumentation do to coverage collection
Interrupt the program (assuming native execution) on a periodic basic to determine its PC,
and map the PC to source line numbers
Run the program under an interpreter, and let the interpreter do it (or let the interpreter make calls on an special user-code event handler when certain key program events occur, such as "function entry").
It may be in fact, that an interpreter doesn't have that ability built-in, in which
case you are reduced to the first solution :-{ If you are running an interpreter, any test coverage data collection it may have built-in should be pretty well advertised in its documentation.
You can likely implement the "interrupt to get PC" method yourself, using symbol data from the link map or the object file (or maybe someone has done it already for you.) It has a serious downside: because you are sampling the PC, it is hard to verify that some function actually got executed. It may have, and you simply didn't sample the PC at the right moment. This is the reason this scheme isn't used in practical test coverage tools.