[
https://issues.apache.org/jira/browse/MAPREDUCE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved MAPREDUCE-512.
--------------------------------------
Resolution: Won't Fix
> Add tests for the DFS HTML and JSP pages
> ----------------------------------------
>
> Key: MAPREDUCE-512
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-512
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Add some basic tests to look for the standard JSP pages on a locally deployed
> MiniMR cluster
> 1. namenode: check that dfshealth is present
> 2. datanode: check that all the datanode JSPs load
> 3. GET the standard servlets.
> The initial checks can just use httpclient to GET the pages; no need (yet)
> for HtmlUnit.
> If the tests were designed to take optional URLs (e.g test.namenode.url and
> test.datanode.url) they could be run against processes brought up
> externally/remotely
> They would
> * help test that the JSP pages are being compiled down and bundled into the
> JARS
> * verify the classpath is getting set up right
> * check that the Jasper engine is working
> * check the servlets are all registering
> I've effectively had to do this in my own code; having a set of these tests
> inside hadoop would make it easier to point the blame at the classpath setup
> or something else.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
