Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED
False Positive from Hobbes Test
wrote...
Technically, if the server returns 404, the location is still "/content/aem6test29/fr.html". If I was to validate a structure I think I would use the exists assertion on the <html> element in this case. But I do agree that the logical it hte node does not exist, that location would return false. Maybe the options should have an "acceptable return codes" so that if you try to validate a forwarding function, you could assert.status(30x).
/Ove
Thanks for your reply. You are of course correct, but nonetheless, it would be nice if I could assert my intention directly rather than indirectly based on something which may or may not be present (I have always found testing for the absence of something rather weaker than something that is explicitly present .. but that's just me).
Yes, I was looking through Hobbes.js hoping to find either an option for the assert.location function I could use to assert the expected response status code, but alas none. Perhaps the guys at Adobe would be prepared to add this ?
Be nice if Hobbes had some better documentation. There are a few overview articles around but other than that it appears you are reduced to having to look through the code itself.
wrote...
.asserts.location verifies the URL in the browser, so if the web server doesn't redirect 404s to an error URL, then .asserts.location is not the good test method.
In such a case, to confirm that you're on the page you want, another page parameter should be tested, for example the page title, or the availability of a specific DOM element.
Thanks. As Ove mentioned above, it would be nice to be able to pass an option to assert.location for the expected status response code. Testing for the absence of something I find a bit naff, but YMMV of course ... and as it stands I appear to have little choice here.
wrote...Yes, I was looking through Hobbes.js hoping to find either an option for the assert.location function I could use to assert the expected response status code, but alas none. Perhaps the guys at Adobe would be prepared to add this ?
This is currently under development, but there is no official ETA.
wrote...Be nice if Hobbes had some better documentation. There are a few overview articles around but other than that it appears you are reduced to having to look through the code itself.
Have you noticed these fairly new pages?
- http://docs.adobe.com/docs/en/aem/6-0/develop/ref/test-api/index.html
- http://docs.adobe.com/content/docs/en/aem/6-0/develop/components/hobbes.html
New content is still being added.
wrote...
wrote...
Yes, I was looking through Hobbes.js hoping to find either an option for the assert.location function I could use to assert the expected response status code, but alas none. Perhaps the guys at Adobe would be prepared to add this ?
This is currently under development, but there is no official ETA.
wrote...
Be nice if Hobbes had some better documentation. There are a few overview articles around but other than that it appears you are reduced to having to look through the code itself.Have you noticed these fairly new pages?
http://docs.adobe.com/docs/en/aem/6-0/develop/ref/test-api/index.htmlhttp://docs.adobe.com/content/docs/en/aem/6-0/develop/components/hobbes.html
New content is still being added.
Good to know that Adobe is considering an update to Hobbes that may include the suggestion above.
Thanks for the links. I was aware of the second but not the first, which was the one I was really looking for :-)
Regards
Fraser
Related Conversations
