BUG - Different behaviour for assertSelectorHasText

[aisingapore]

BUG - Different behaviour for assertSelectorHasText

[kensoh]

For CasperJS testing framework if you want to check text for the page body you can consider using this.assertTextExists() - http://docs.casperjs.org/en/latest/modules/tester.html#asserttextexists

[thim81]

Additional, I use assertSelectorHasText to check if a text exists in the page, perhaps there are better checks for this?

I looked in the CasperJS documentation and Google but none of them gave me a working solution.

[kensoh]

Hi @thim81 yes this is expected. The testing framework for CasperJS is not usable with running on Chrome as CasperJS does not support Chrome at the moment. I added that note in the testing section, and also another note at the start of developers reference with a recommended list of open-source tools that can be used for test automation. This is because there are many established tools that can do a great job at specifically testing. https://github.com/tebelorg/TagUI#testing

[kensoh]

Actually CasperJS testing framework is expressive and really good at that time when it was introduced. My only guess is due to other frameworks such as NightmareJS moving to the more popular Electron browser, and that being centrally developed instead of having a plug-and-play model, over time I don't think the testing framework become the leading approach for developers / test automation engineers.

[kensoh]

This issue can probably be closed, I think I can update the readme to make it clearer. There are some updates to improve readme clarity from a couple of your closed issues as well.