[Cosmo-dev] Automated Functional Test Coverage

[Mikeal Rogers]

None of the new features for 0.7 are automated. Adam just finished  
fixing most of the old calendar UI tests.

We intend to automated all of the dashboard and other new features in  
cosmo that are in the 0.7 test spec -- it's doubtful we have enough  
time to do _all_ off them but that's still the goal. There is nothing  
blocking us, technology wise, from automating everything.  
Occasionally we need some assistance from development to have a  
repeatable way to get an element id, but that's about it. There isn't  
a separate list of things we are attempting to automate because we  
want to automate all of it.

In the last release we had all of the calendar UI automated, it would  
be great if we could do the same for the dashboard.

I think a column that keeps track of what we've completed automating  
in the 0.7 test spec is a great idea.

-Mikeal

> Cosmo 0.7 test spec just enlists all the cosmo 0.7 features under  
> test. That does not cover which ones have been tested by Windmill.
>
> One idea is we can add a column to the test spec itself to include  
> which ones are manual v/s automated. That avoids the need for  
> having a seperate wiki page for listing all the automated tests.
>