Selenium WebDriver and Play

I have advocated tests using Selenium WebDriver in the past many times. Will it become a de facto standard now that frameworks like Play make it very easy ?

It is not even evident below that Selenium WebDriver is being used. It is HTMLUNIT that is imported statically.

A test server is started, a test application is setup and a browser is simulated, all in a few lines of code. Very economical.

import static org.fest.assertions.Assertions.assertThat;
import static play.test.Helpers.*;

import org.junit.Test;

import controllers.routes;
import play.Logger;
import play.libs.F.Callback;
import play.test.TestBrowser;
import static helpers.TestSetup.*;

public class ProposalSubmissionTest {

	@Test
	public void proposalTest(){
		running(testServer(3333,fakeApplication(testDbSettings())),HTMLUNIT, new Callback<TestBrowser>(){

			@Override
			public void invoke(TestBrowser browser) throws Throwable {
				browser.goTo("http://localhost:3333" + routes.MainController.newProposal().url());
				assertThat(browser.title()).isEqualTo("New Proposal");
				Logger.debug(browser.title());
			}
			
		});
	}
}

Play User Interface Lesson

I have just completed the UI using Play’s assets. I need to explore the asset controller and compiler. This seems to be interesting and is not part of any Java framework I have used.

I had to install Sass

Play framework form validation errors

I post as I work my way through the Play material. I have not still read The reactive manifesto and relate it to Play. So I used the same classic trick popularized by Struts to debug this. As far as this type of error display mechanism is concerned I did not find anything different between Play and old versions of Struts.

Problem

I did not initialize isApproved to false.

package models;

import javax.persistence.*;
import javax.validation.Valid;

import play.data.validation.Constraints.MaxLength;
import play.data.validation.Constraints.MinLength;
import play.data.validation.Constraints.Required;
import play.db.ebean.*;

@Entity public class Proposal extends Model {

	@Id
	public String id;
	
	@Required public String title;
	
	@MinLength(value = 10)
	@MaxLength(value = 1000)
	@Column(length=1000)
	public String proposal;
	
	@Required public SessionType type = SessionType.OneHourTalk;
	
	@Required public Boolean isApproved;
	
	public String keywords;
	
	@Valid
	@OneToOne(cascade=CascadeType.ALL)
	public Speaker speaker;
}

Display errors

@(proposal: play.data.Form[Proposal])

@import helper._


@main("New Proposal"){

	@if(proposal.hasErrors) {
        <div class="alert alert-error">
            @proposal.errors
        </div>
	}

	@form(action = routes.MainController.submitProposal()){
	<h3>Proposal</h3>
    @inputText(proposal("title"))
    @textarea(proposal("proposal"))
    @inputText(proposal("keywords"))
	<h3>Speaker</h3>
    @inputText(proposal("speaker.name"))
    @inputText(proposal("speaker.email"))
    @textarea(proposal("speaker.bio"))
    @inputText(proposal("speaker.twitterId"))
    @inputText(proposal("speaker.pictureUrl"))
    
	<p class="submit">
				<button type="submit" class="button green" id="submitForm">Submit</button>
	</p>
    }
}

Error message

I can customize it but this sufficed.

Default settings for Play Java applications

I started worked with a play example and encountered this error.

package controllers;

 

import models.Proposal;

 

import play.data.Form;

import play.mvc.Controller;

import play.mvc.Result;

import play.mvc.Results;

import models.*;

 

public class MainController extends Controller {

  

    public static Result welcome(String name) {

        return ok("<h1> Welcome " + name + "</h1>").as("text/html");

    }

 

    public static Result index() {

        return ok(views.html.index.render("Hi from Java"));

    }

    

    public static Result newProposal(){

    Form<Proposal> proposalForm = Form.form(Proposal.class);

    

    return ok(views.html.newProposal.render(proposalForm));

    }

    

    public static Result submitProposal(){

    return Results.TODO;

    }

    

}

Error

[error] /Users/radhakrishnan/Documents/hello-play/app/controllers/MainController.java:23: error: incompatible types: play.data.Form cannot be converted to play.api.data.Form
[error] return ok(views.html.newProposal.render(proposalForm));

I struggled with this error until I set play.Project.playJavaSettings in my build.sbt

Play Framework

I was trying to use the activator UI to play with the Play Framework. It worked except for this annoying issue.

So I switched to the eclipse setup which works quite well.

[hello-play] $ Mohans-MacBook-Pro:hello-play radhakrishnan$ ./activator
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
[info] Loading project definition from /Users/radhakrishnan/Documents/hello-play/project
[warn] Multiple resolvers having different access mechanism configured with same name ‘typesafe-ivy-releases’. To avoid conflict, Remove duplicate project resolvers (`resolvers`) or rename publishing resolver (`publishTo`).
[info] Set current project to hello-play (in build file:/Users/radhakrishnan/Documents/hello-play/)

Generate an eclipse project

[hello-play] $ eclipse with-source=true
[info] About to create Eclipse project files for your project(s).
[info] Resolving com.typesafe.atmos#atmos-sigar-libs;1.3.1 …
[info] downloading http://repo1.maven.org/maven2/org/scala-lang/scala-library/2.10.2/scala-library-2.10.2-sources.jar …
[info] [SUCCESSFUL ] org.scala-lang#scala-library;2.10.2!scala-library.jar(src) (41827ms)

Change and save

Hot deploy

[hello-play] $ ~run

— (Running the application from SBT, auto-reloading is enabled) —

[info] play – Listening for HTTP on /0.0.0.0:9000

(Server started, use Ctrl+D to stop and go back to the console…)

[success] Compiled in 715ms
[info] play – Application started (Dev)
[info] Compiling 1 Java source to /Users/radhakrishnan/Documents/hello-play/target/scala-2.10/classes…
[success] Compiled in 4s

— (RELOAD) —

[info] play – Application started (Dev)

Change in view