As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm starting using Selenium webdriver to write auto test scripts for an ajax website mainly on Chromedriver by using JAVA. The website is coded by using HTML 5. it's actually a website mainly used on mobile devices like iphone, android.
I don't know which framework to choose. I saw TestNG, JUnit. And someone suggested me to use Fitness.
I'm confused on choosing a proper framework.
Can anyone give me some suggestions? thanks in advance.
This is a question on opinions, there's no definite answer. You should go with the framework that fits you best.
JUnit is generally (from my point of view) considered more standard to Java testing and is usually integrated to Java IDEs, but TestNG has some advanced features one might like (and its integration is usually very easy, too). FitNesse is a different story, the tests in it are written quite differently. In JUnit and TestNG, you write the test cases in plain Java, but FitNesse works ... different. And it's by far the least common.
All those frameworks work well with Selenium, you can find examples on all of them all over the internet.
If you're really just starting with WebDriver and Java, go for JUnit, as it's usage won't limit you for a very long time and it's quite easy to begin with.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm writing a webapp that uses websockets for updating vehicle positions on a google map and for exchanging messages with drivers in realtime. I've been playing around with Node.js as well as Tornado, but I've come to the conclusion that I'd prefer static typing for this project after all.
Two excellent choices seem to be Scala and Go, but I'm having a hard time deciding between those two. I've been mostly been programming in C/C++/C#/Python and have very little Java experience.
So how do those two compare? What would you learn next? I know this is subjective, but I'm kind of looking for some battle stories here. Also, what about the ecosystem? From what I can tell, Scala inherits Java's ecosystem, but what about Go?
The down side of Go - immature, with very little real world experience.
The down side of Scala - you must be familiar with the Java eco system in order to utilize scala well. You probably can't write everything in Scala. Also, some might find the learning curve for Scala higher.
Both supports websockets (Scala through Lift for instance, and Go in the standard library).
I believe that you'll be more comfortable with Go, since it's more similar to Python than Scala.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Did someone have succeed stressing a GWT app?
Any recommended tool?
I wrote a blog post about this topic a little while ago.
http://blog.oio.de/2011/04/19/load-testing-gwt-applications-with-selenium-2-and-gradle
There I published a Selenium 2 test script written in Groovy and a Gradle script for the parallel execution.
But with this solution and no accessibility from the outside its quite difficult to put a heavy load on your GWT application. Except you have many free test clients available in your work/dev environment.
We are successfully using http://loadui.org to test our GWT app. To test the GUI we input directly JSON HTTP requests to our RPC servlet. It's also useful to test SOAP/REST web services.
http://loadstorm.com/ is a great tool which lives in the cloud and supports Javascript. Fairly powerful and easy to setup and use.
We use NeoLoad for our GWT load tests campaigns. They provide an easy way to describe the JSON calls in the GUI.
You should check this out here to see if it can help you as well!
My Company (UBIK-INGENIERIE) distributes a commercial Apache JMeter plugin to load test GWT and GWT RPC applications.
You can easily record, variabilize and replay GWT and GWT RPC based application with standard knowledge of Apache JMeter.
See:
http://www.ubik-ingenierie.com/blog/load-testing-gwt-rpc-applications-with-ubik-load-pack-plugin-for-jmeter/
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am evaluating web frameworks. The criteria is lightweight, secure, easy to learn and deploy. There're plenty, but I come up with the following short list,
web2py - the python version of "ruby on rails"
wt. - desktop version of web application
CGI/Perl - the old buddy
Have you worked with any of the above web frameworks and what's your experience? If not, which one do you recommend instead?
Thanks,
This is a flame war in the making.
why did you rule out django and RoR, they have a lot more developer support.
Evaluation of a framework is subjective. A framework is only as good as how good you are with a language, and best practices of a language. What works for one programmer or team, may not work for another, if the team is full of people new to the language.
Please rephrase your question, or rather think about if you really need a framework in the first place.
I find RoR feels very light and is easy to learn. I've also developed in several Java-based frameworks - though all feel heavier than RoR but certainly are rich in features.
Don't know how to comment on answers. To answer Klochner, both seems quite popular but Ruby is not a language that I am familiar with and Django seems more heavy and complex to me than web2py.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I need a free very simple CMS which i can host on my own server just like Cushy CMS www.cushycms.com. is there any ?
I recently wrote an alternative to CushyCMS because I wanted the open source community to have a free alternative.
Mechedit is an open source CushyCMS like applciation. Runs on PHP5 only though.
Orbis CMS is another open source alternative to CushyCMS. It's built on the same pricinples (simplicity, ease-of-use) and features a stylish interface, but is self-hosted and free.
SnappySnippets is a free and simple alternative; it is highly customizable and has a desktop interface that your clients will find easy to use. It is hosted so that you don't have to install anything
There are many questions like this on Stackover flow
for example:
link text
Just search for CMS
Good question which I was asking myself recently. This is a neglected corner of the CMS landscape. However, I did find:
this rather detailed and intelligent summary list:
http://www.matthijskamstra.nl/blog/index.php/2011/02/16/lightweight-cms-for-simple-projects/
a briefer but recently updated list of 40 lightweight CMSs http://www.abcphp.com/out/top-40-free-simple-lightweight-cms-|-vivalogo-resources/
Two other lists, both from 2012 and neither suggesting much examination of the products:
http://webdesignledger.com/tools/10-simple-and-light-weight-cms-solutions
http://speckyboy.com/2010/07/19/14-light-and-east-to-use-open-source-content-management-systems/
In case you're wondering, the project I was looking at using one of these for got a little more complicated and I ended up going to a more heavyweight system, with a simplified interface on top of it.
There's a lesson there. Many systems that will cope with complex needs (Drupal, MODX etc) can still be installed pretty quickly, and your users' needs are only going to grow more complex over time.
That said, I'd still like to think lightweight systems have their place. Let us know what you chose.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
How does the IDEA Community Edition compare with Eclipse?
IDEA is a far better IDE than Eclipse (general opinion by people that use IDEA).
On a feature point of view, everything that IDEA CE can also been done by Eclipse. However,
IDEA is a commercial product, which limits its adoption. Thanks to the Community Edition, you can test this IDE for free, in order to develop JavaSE applications (or Scala or Groovy). For an enterprise, this is quite limited, as you will not be able to develop J2EE applications.
My conclusion is that IDEA CE is only a tool that allows you to test and understand the philosophy of this IDE. If you are convinced by IDEA, then you will really have to choose between the Ultimate Edition, which will let develop any kind of applications, or stay with Eclipse.
The best, straight answer to this, is to look at the feature matrix of which features are still left in Ultimate-Edition. Eclipse probably has support for all of these things, although the quality of the integrations can always be an issue.
Why IDEA:
detects unused public fields and methods
easy way to run or debug only one test method (you don't need to modify configuration)
faster code coverage report generation (at least for EMMA)
understand difference between source and test source
easier way to manage libs - just include lib dir (in eclipse you have to specify all jars explicitly), so you don't have to update it manually every time when new jar was included