Anyone successfully use TestStack White tools for Reporting/Logging?

361 views
Skip to first unread message

Mike Hetzer

unread,
Jul 12, 2016, 5:03:06 PM7/12/16
to TestStack.White
I have just completed a short project where we used TestStack White to automate a WPF application.

We created our own base framework and Page Object Model similar to what you would see with a typical Selenium Project.

I had seen that TestStack White has some functionality for logging messages and events to reports and also a HTML Report Generator, unfortunately I did not have time to investigate this path and we simply decided to use NLog and do simple reports by writing to text files.

I was hoping someone could maybe share some steps, class files, or any helpful links/tutorials to use TestStack White for reports.

Imre Lengyel

unread,
Oct 11, 2016, 1:35:51 PM10/11/16
to TestStack.White
Hi Mike,

Was there a reason why you wrote your own over using ScreenObjects? I am asking since we are still ramping up our testing so there might be some painful downsides which I have not seen yet. So far this is what I see:
The Good:
  • Convention based specification, with UiItem fields automatically assigned.. can also specify attributes to help matching
  • The previous point promotes you to structure the page objects quite nicely
  • Appears that the reporting which you asked for is built in but I have not tried it yet, I only reviewed the source so I am not sure if it works. 
The Annoying:
  • Since the fields are assigned using castle proxies, all members of AppScreen  or AppScreenComponent will need to be virtual.. I will tack on https://github.com/Fody/Virtuosity if this becomes too annoying.
  • The documentation is very thin and fragmented. Appears that the best source of documentation is the source and samples.
The Ugly:
  • I have not seen anything major yet.
cheers,

Mike Hetzer

unread,
Oct 11, 2016, 2:47:46 PM10/11/16
to TestStack.White
Well, basically for this project we went with a more custom framework because
A.) The base was created by someone else I work with while I was assigned another task
B.) Neither I nor he knew how to implement ScreenObjects or the TS.W Reporting properly

We ended up going with a custom HTML report as well that reports results in a tabular format.

We still follow common practices like using a Page Object Model, Unit Test Framework using NUnit, additional logging using NLog.

Sometimes I'd still like to see or figure out how to use TS.W Reporting, but there's not much documentation except for the source. If I could have figured that out we may not have needed to reinvent the wheel.
Reply all
Reply to author
Forward
0 new messages