How to capture the screenshot?

To capture the screenshot use the following code,

E.g.,

1) Browser("name:=Google Maps").Page("title:=Google Maps").CaptureBitmap "c:\Googlemaps.bmp"

2) Browser("micclass:=Browser").Page("micclass:=Page").CaptureScreenshot micPass, "Page ScreenShot."

3) Reporter.Reportevent micPass,"Screenshot Capture","Screenhot Captured."&strFileName&" Is the file name"      ‘To report with a screenshot

Comments

Post a Comment

Popular posts from this blog

Is QA a easy job?

 Many people think that assuring the quality is a easy job but it is not so. I have a professional experience of 10+ years in Software testing. Initially I felt more satisfied and did more work technically but now I feel boring and frustrated with lot of work and hear people comment..testing is so easy.. I have heard this often in my team itself. So many dependencies in accomplishing a simple job.  And another thing, when people is tired of searching a job, many of my friends finally will ask....how to land in a QA job as it is the  easy one.How cum this is spreading ? Remember, no job is easy and think before you comment.
Read more

Latest Version of TestComplete

 TestCompletes latest version as of February 2023 is -  15.48.6 (Jan 31, 2023) TestComplete supports various testing types and methodologies, for example: Functional and GUI testing Unit testing Regression testing TestComplete has 3 window layouts: Design-time - used when you view and edit tests, Recording - used when you record tests, Playback - used when you run and debug tests.
Read more

Successful tester

  Software Tester must  possess the below guidelines  t o be successful, • Concise:  As simple as possible and no simpler. • Self-Checking:  Test reports its own results; needs no human interpretation. • Repeatable:  Test can be run many times in a row without human intervention. • Robust and logical:  Test produces same result now and forever. Tests are not affected by changes in the external environment.  • Sufficient:  Tests verify all the requirements of the software being tested. • Necessary:  Everything in each test contributes to the specification of desired behavior. • Clear:  Every statement is easy to understand. • Efficient:  Tests run in a reasonable amount of time. • Specific:  Each test failure points to a specific piece of broken functionality; unit test failures provide "defect triangulation". • Independent:  Each test can be run by itself or in a suite with an arbitrary set of other tests in any order...
Read more