Tools to take screen shots

SnagIt Built-in Windows capture: Ctrl-Alt-PrtSc. Then Paint, if needed, to trim off any extraneous portions. FastCapture Camstudio MWSnap (http://www.mirekw.com/winfreeware/mwsnap.html) Jing from TechSmith Fullshot Greenshot TestDrive-Assist from Original Software www.orgisoft.com this tool is designed for manual testing for QA and BA specialists. Not only screen shots, but full content and annotation with built in quality checks like, spelling, link and title. Launch Telerik WebUI Test Studio 2010.2t is best software for Functional Testing and also take screenshots & prepare document for that Screenhunter (http://wisdom-soft.com/products/screenhunter_free.htm) Faststone Camstudio Captura 20/20 (http://www.sofotex.com/20/20-download_L230.html) Clip2net If you are using Firefox, a firefox add-on is available named 'FireShot'. Just try it for taking screenshot. It can also be added as a add-on in Internet Explorer too. Irfanview (http://www.irfanview.com) Firefox has pixslr grabber, so you need firefox as a browser Mezer Tools (http://www.fiddlertool.com/mezer/) Testuff, our test mangement tool, allows taking screenshots while running a test. ScreenpressoFastStone Capture for Images Screen2Exe for Video Vienna - Test Management' to automatically capture a screen shot when you raise a defect during test execution. (http://www.nmqa.com/DownloadViennaTestManagement.aspx) ScreenHunter Zap Grab Picasa Cropper capture Evernote (http://www.evernote.com/) HyperSnap Scap (http://www.1202performance.com/tools/screen-capture/) PicPick - http://www.picpick.org/ Fireshot - http://screenshot-program.com/fireshot/ Bugshooting.com BugDigger automatically attaches web page screenshot, environment details and other useful data to your bug report. http://bugdigger.com For manual test execution - HP Sprinter!!!! This is a very good tool that gives the tester many cool staff and helps the tester to execute test much faster. One of the build it capability is to report a defect with annotation as well as send screenshots with annotation. Additional cool staff in HP Sprinter: - Automatic data injection - Improved Usability and UI - the tester don't need to toggle between the test and the application under test - Informative reports - Semi automatic steps (record & replay) - Mirror - The only tool the supply a way to validate many testing environments in one test execution

Testing a web-based application

Testing a web-based application 1. SoapUI (http://www.soapui.org/) 2. JMeter (http://jakarta.apache.org/jmeter/) 3. Selenium 4. QTP 5. Load Runner 6. Open STA (http://www.opensta.org/) 7. Watir 8. QMetry 9. loadstorm http://www.youtube.com/watch?v=OfDQzPWIWts http://www.youtube.com/watch?v=NqMFitl8koo http://www.toolsjournal.com/79/listview/search/play

Plan QA Schedule for Release

I am documenting all the following points on the basis of my experience, if you find any ambiguity; please provide me your valuable feedback comment so that I can make the corrections. Before you plan any QA Schedule for the release, consider the following points to take: Name of Release List of various tasks Expected duration for particular task Expected start of particular task Expected finish of particular task Resources to be involved in particular task Actual start of particular task Actual finish of particular task Predecessors List of high level tasks in the Release Planning Analysis Design Execution Reporting Closure Activities Tasks activities in planning phase Get Dev Schedule to build QA Schedule (Dependency) Get Environment Information Finalize Test Schedule Create Scope Doc Tasks activities in Analysis phase Analyze BRS & Mockups and Send Questions/Findings RAA session to answer questions Review and Analyze RAA Answers and prepare list of changes to TCs Tasks activities in Design phase Develop positive and negative Test Scenarios Review Scenarios Develop positive and negative Test Cases Peer Review of Test Cases + Fixing Findings Create RTM Copy TCs to Other Test Beds Folders (after Review and Before Execution) Create Test Data (if needed) MILESTONE: Test cases are finalized - Execution can begin Tasks activities in Execution phase Smoke Test Select Smoke Test Cases to be executed Execute Smoke Test Cases Evaluate Build (Functional Test GO/No GO) Functional Cycle Execute test Cases Retesting fixed bugs Regression Cycle Select Test Cases to be executed Start Code Freeze & Execute Regression test Cases Defect Management Buffer/Contingency- Unexpected delay from Dev/QA, Unexpected failures, bugs not fixed from first time, bad deployments, …etc UAT Cycle (release day) Execute test Cases Give feedback (Production GO/ No GO) Tasks activities in Reporting phase Give TCs Development Report Give Execution Report Give Defect Report Tasks activities in Closure Activities phase Fill in lessons learned sheet Consolidate & Give Lessons Learned sheet Get Sign off Abbreviations RAA – Requirement Ambiguity Analysis RTM – Requirement Traceability Matrix UAT – User Acceptance Testing TC – Test Case QA – Quality Assurance

Macro utilities for Excel

Sub ClearData() ' ClearData Macro For RowC = 5 To Worksheets.Count RowX = "A" & RowC 'Modify Letter for Column Range(RowX).Select Selection.Hyperlinks(1).Follow NewWindow:=False, AddHistory:=True Range("I16:J16").Select Selection.ClearContents Sheets("Report").Select Next RowC ActiveWorkbook.Save End Sub Sub NoRun() ' NoRun Macro For RowC = 5 To 9 RowX = "A" & RowC 'Modify Letter for Column ' Range(RowX).Select Selection.Hyperlinks(1).Follow NewWindow:=False, AddHistory:=True Range("J16").Select ActiveCell.FormulaR1C1 = "No Run" Sheets("Report").Select Next RowC ActiveWorkbook.Save End Sub Public Sub Get_Report() Dim i As Long For i = 2 To Worksheets.Count ActiveSheet.Cells(i, 1).Value = Worksheets(i).Name ActiveSheet.Cells(i, 2).Value = Worksheets(i).Cells(3, 8).Value ActiveSheet.Cells(i, 3).Value = Worksheets(i).Cells(3, 3).Value ActiveSheet.Cells(i, 4).Value = Worksheets(i).Cells(16, 10).Value ActiveSheet.Cells(i, 5).Value = Worksheets(i).Cells(16, 9).Value Next i End Sub Sub hyperlink() ' ' hyperlink Macro ' Application.ScreenUpdating = False Dim hyper As String ' hyperlink variable ' Dim endrow As Integer Dim RowX As String ' Cell to change Dim RowC As Integer 'row Counter Dim wb As Workbook Dim ws As Worksheet Set wb = ThisWorkbook Set ws = wb.ActiveSheet endrow = ws.Cells(ws.Rows.Count, 1).End(xlUp).Row RowC = 2 Do Until RowC > endrow RowX = "A" & RowC 'Modify Letter for Column Range(RowX).Select If Range(RowX).Value <> "" Then ' skips cell if blank hyper = Range(RowX).Value Range(RowX).Hyperlinks.Add Anchor:=Selection, Address:="", SubAddress:= _ "'" + hyper + "'!A" + CStr(RowC) _ , TextToDisplay:= _ hyper End If RowC = RowC + 1 Loop Application.ScreenUpdating = True End Sub

Decide What Test Cases to Automate

It is impossible to automate all testing, so it is important to determine what test cases should be automated first. The benefit of automated testing is linked to how many times a given test can be repeated. Tests that are only performed a few times are better left for manual testing. Good test cases for automation are ones that are run frequently and require large amounts of data to perform the same action. You can get the most benefit out of your automated testing efforts by automating: Repetitive tests that run for multiple builds. Tests that tend to cause human error. Tests that require multiple data sets. Frequently used functionality that introduces high risk conditions. Tests those are impossible to perform manually. Tests that run on several different hardware or software platforms and configurations. Tests that take a lot of effort and time when manual testing. Success in test automation requires careful planning and design work. Start out by creating an automation plan. This allows you to identify the initial set of tests to automate, and serve as a guide for future tests. First, you should define your goal for automated testing and determine which types of tests to automate. There are a few different types of testing, and each has its place in the testing process. For instance, unit testing is used to test a small part of the intended application. Load testing is performed when you need to know how a web service responds under a heavy workload. To test a certain piece of the application’s UI, you would use functional or GUI testing. After determining your goal and which types of tests to automate, you should decide what actions your automated tests will perform. Don’t just create test steps that test various aspects of the application’s behavior at one time. Large, complex automated tests are difficult to edit and debug. It is best to divide your tests into several logical, smaller tests. It makes your test environment more coherent and manageable and allows you to share test code, test data and processes. You will get more opportunities to update your automated tests just by adding small tests that address new functionality. Test the functionality of your application as you add it, rather than waiting until the whole feature is implemented. When creating tests, try to keep them small and focused on one objective. For example, separate tests for read-only versus read/write tests. This allows you to use these individual tests repeatedly without including them in every automated test. Once you create several simple automated tests, you can group your tests into one, larger automated test. You can organize automated tests by the application’s functional area, major/minor division in the application, common functions or a base set of test data. If an automated test refers to other tests, you may need to create a test tree, where you can run tests in a specific order. Reference: www.automatedqa.com

Time Estimation for automated scripting

Hi, I am taking one real time scenario for any desktop/web based applications need to be automated e.g. Retail application. And tool to be used is QTP or TestComplete. Requirement- 2000 Manual Test Cases need to be converted into automated scripts mainly for regression testing. Main points to initiate discussion or estimating the time required- How many products are there. How many transactions are there. How many type of customer are there. Which framework is to be followed. (Most of the cases, Hybrid Framework is preferred) Way to proceed Identify key areas (primary) e.g. main functionality, financial, important feature, etc. Identify number of features e.g. 100. Identify complexity of features (medium, high or low) Divide the deliveries into different phases P1, P2 and P3. Time Estimation Go screen by screen. Identify time for single screen e.g. 45min, 50min, etc. High complexity scripts having more than 10 screens normally requires 8 hours time. Medium complexity scripts having less than 10 screens requires 4 to 6 hours time depending on the number of screens. Say you have identified that applications requires only 100 scripts, now divide all deliverables into different phases- Phase1 - Study the application and gather requirement. Phase2 - Deliver 10 automated scripts (mainly key features). Phase3 - 20 Scripts Phase4 - Another 20 Scripts - - And so on.... Implementation Choose products Use parametrization using local/global sheets. Do record/play in the initial phase. Enhance your scripts by applying various checkpoints,etc and see the behavior. If things goes well, then it is good otherwise go for descriptive programming. Create actions per transactions. Identify transactions that can be reusable e.g. login, logout, various actions to be used multiple time in the application. Applying Recovery Scenarios in case screen is stucking at some point/

Automation Frameworks