How to approach the UI workflow test which involves multiple URL links

[sparupat]

Abigail,

Thanks a lot for creating infrastructure for acceptance testing.

I have setup nightwatch framework for acceptance testing and I am planning to write test to check where

1. User logs in to the account as admin
2. Go to a specific route and performs UI actions

Can you please suggest me a way to implement the workflow?

[awatson1978]

Hi sparupat, Thank you for the kind words. Just as an FYI, the clinical:nightwatch package has been deprecated in favor of the starrynight utility. They're both compatible with each other, but StarryNight offers way more functionality and is where all the current Nightwatch development is currently taking place.

It's funny you ask about documentation on the ActiveEntry pattern, as that's on my list of things to do next week. I've implemented what you're asking for a dozen times, but usually for work-for-hire projects, and the pattern hasn't been entirely opened and documented yet.

In the meantime, you can take a look at the Clinical Trials demo app, which has most of the ActiveEntry pattern scripted out in walkthrough, but not componentized or refactored into custom commands.
https://github.com/awatson1978/clinical-trials/tree/master/tests

It's also worth taking a look at the Component Input and Component Output sections of the StarryNight Testing Manual.
http://starrynight.meteor.com/testing

If you can hang out for another couple of weeks, we're going to have the ActiveEntry pattern refactored into a series of packages, along with a tutorial walkthrough written up. In the meantime, the Clinical Trials tests should get you started with the basic workflow, even if it's not entirely organized in a componentized manner.

Cheers! :)