|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Class Summary | |
---|---|
AbstractAuthenticatedTest | This class consists of utility methods for writing tests which use authentication. |
AbstractSlingResourceTypeRenderingTest | Base abstract test for creating a Node and rendering it using scripts in various supported languages, using slingResourceType-based script resolution |
BundleContentTest | |
ContentLoaderMiscPropertyTest | Test that property types are supported in initial content. |
CreateNodeTest | Test creating a Node using the MicroslingIntegrationTestClient |
DavExIntegrationTest | Test of Davex |
EspLoadTest | Test the SLING-428 esp load function |
ExecuteScriptTest | Test the executeScript test method |
FileUploadTest | Test uploading files to the Sling repository via WebDAV, as a first step towards testing the complete content creation and rendering scenario. |
FiltersTest | |
ForwardTest | Test the {link ScriptHelper#forward) functionality |
GeneratedNodeNameTest | Test the generation of node names for POST requests to URLS ending in / * |
GeneratedNodeNameTestStar | Test the generation of node names for POST requests to URLS ending in / * |
GetStarTest | A GET to *.html and *.json must work even if there is no Node at the specified path (SLING-344) |
GetWithSuffixTest | GET requests with a suffix should fail with a 404, otherwise we get a lot of extra possible URLs which point to the same content. |
HttpPingTest | Ping the Sling server to verify that our integration test setup is ok. |
IncludeTest | Test the {link ScriptHelper#include) functionality |
InitialContentTest | |
JavascriptWrappersTest | Test Scriptable objects |
JsonQueryServletTest | Test the {link JsonQueryServlet) functionality. |
JsonRenderingTest | Test creating Nodes and rendering them in JSON |
JspForwardTest | Test the {link ScriptHelper#forward) functionality |
JspIncludeTest | Test the {link ScriptHelper#include) functionality |
JspScriptingTest | Test JSP scripting TODO this class can be generalized to be used for any scripting language, that would help in testing all scripting engines. |
JspTestBase | Base class for tests that use JSP - configures the JSP scripting engine in a test-friendly way |
LaunchpadConfigInstallerTest | Verify that the test config is installed |
MkdirTest | Test the MicroslingIntegrationTestClient's mkdir functions |
NamespaceMappingTest | Test that both Sling-Namespaces and NamespaceMapper work. |
NodetypeRenderingTest | Test creating a Node and rendering it using scripts in various supported languages, using nodetype-based script resolution |
PostRedirectTest | Test the various redirect options for POST, SLING-126 |
PropertyRenderingTest | Test the rendering of JCR Properties, directly addressed by URLs. |
RangeStreamingTest | The RangeStreamingTest tests the Range request header support
for the StreamRendererServlet introduced with SLING-1814 |
RedirectTest | Test creating Nodes and rendering them in JSON |
RenderingTestBase | Base class for rendering tests |
RequestAttributeTest | Test the "org.apache.sling.api.include.servlet" and "org.apache.sling.api.include.resource" request attributes with the {link ScriptHelper#include) functionality |
ResourceDecoratorTest | |
ResourceSuperTypeTest | Test resource supertypes |
ScriptBindingsValuesProviderTest | |
ScriptBuiltinObjectsTest | |
SlingResourceTypeRenderingTest | Test creating a Node and rendering it using scripts in various supported languages, using slingResourceType-based script resolution |
StaticContentTest | Some tests about static content |
StreamServletTest | Test the streaming of static files uploaded to the repository |
SyntheticResourceTest | Test the SLING-129 SyntheticResource , by requesting
non-existent Nodes.. |
UploadFileTest | Test uploading files using the Sling post servlet (SLING-168) |
ValueFromTest | Test the @ValueFrom field name suffix, SLING-130 |
WebdavUploadTest | Test WebDAV upload of various file types |
The tests found in and under this package are used in the "integration-test" build phase (SLING-82), they are not run as part of the normal "test" build phase.
To debug the integration tests, however, it is useful to run them as part of the normal test phase, after starting a separate Sling instance that they can talk to.
This is implemented using Maven profiles: to run the integration
tests during the normal test phase, disable the "disableIntegrationTestsInTestPhase"
Maven profile, for example using mvn -P nullUslingProfile test
.
See pom.xml for more details.
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |