Do We Need To Build Reporting Logging Etc ?

1.	Do We Need To Build Reporting Logging Etc ?
Answer» No, Sahi automatically logs all statements that are executed, without the tester ADDING any CODE. It also builds a summary REPORT in HTML of all SCRIPT executions in a suite. No, Sahi automatically logs all statements that are executed, without the tester adding any code. It also builds a summary report in HTML of all script executions in a suite.

Answer»

No, Sahi automatically logs all statements that are executed, without the tester ADDING any CODE. It also builds a summary REPORT in HTML of all SCRIPT executions in a suite.

No, Sahi automatically logs all statements that are executed, without the tester adding any code. It also builds a summary report in HTML of all script executions in a suite.

Discussion

No Comment Found

Related InterviewSolutions

Do We Need To Build Reporting Logging Etc ?
Ok, Once I Have A Few Scripts, Can I Run Them In Batch? Can I Hook Into My Continuous Integration System?
Does It Support File Uploads And File Download Dialogs?
What About Popup Windows?
My Application Uses Lots Of Frames And Iframes. How Does Sahi Handle This?
One Of The Main Problems In Our Current Browser Automation Is That We Need To Add Waits Everywhere. Can You Add Waits In Sahi?
What Is Xpaths?
How Does Sahi Identify Elements?
That Was A Useful Digression On Automation Code. Coming Back To Sahi, How Does Sahi Work With Various Browsers? Do I Need To Write Separate Scripts For Each Browser?
I Have Heard That Testing Code Is Like Development Code. It Needs To Be Architected, Refactored And Maintained Like Production Code?

Do We Need To Build Reporting Logging Etc ?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment