Pages

Sunday, September 18, 2022

Rough idea for automation of manual testing

 Steps  

  1. Calculate return on investment  

  1. Create/list need of automation  

  1. Validate the need  

  1. Discuss with testing team  

  1. Discuss its automation cost 

  1. Find high level possible gaps  

  1. Validate the automation cost   

  1. POC of Automation  

  1. With a web page 

  1. With a desktop app  

  1. Validate POC with technical team  

  1. Understanding between testing automation Need and Testing Automation 

  1. Get high level testing points for automation  

  1. Testing types 

  1. All input and output  

  1. Document of understanding between testing team and automation team  

  1. Validate the discussion  

  1. Plan the map of automation  

  1. Validate and review the plan of automation  

  1. Create a team of manual testers and automation engineers  

  1. Automation team:  

  1. Finalize framework  

  1. Inherit existing framework  

  1. Do again a POC with framework  

  1.  Discuss and finalize on low levels  

  1. Strategy of automation testing  

  1. Understand the product  

  1. Finalize high level modules to test 

  1. Finalize testcases for automation  

  1. Get idea about test data  

  1. Finalize test server / accounts  

  1. Finalize reporting / Log of test results / email/ table output  

  1. Finalize process of manual validation of test results  

  1. Integration with ADO 

 

 

 

Notes:  

Automation Testing team standards  

  1. Validation of page  

  1. Title and subtitle of page  

  1. Page ROI 

  1. Data  



Testing Process - Steps for Approval of test cases

 Its a very important process to implement approval process of testcases. 

Objective of peer approval

1.  Crosscheck each other 

2. Peer knowledge of an assigned project

3. Strengthen team knowledge 

4.  Strengthen team relationship

5. complete project with time  


Thursday, June 2, 2022

Build & Implement standards for writing testcases

What Is a Test Case in Software?

A test case is exactly what it sounds like: a test scenario measuring functionality across a set of actions or conditions to verify the expected result. 

 Standards/ Random ideas for writing a testcase:  

  1. Find the right master suite for a test case in your test management studio . Create a new suite if needed. 
     

  1. Mention Right Area path and Iteration for a test case (Area path and Iteration are terms used in Azure DevOps. )

  1. Maintain the title of a test case as per QC standards of your Company
     

  1. The title needs to be precise and easily readable as per project. Feature, sub-feature and verification statement  

  2. Manage Order of Testcases for easy execution of test cases. This will be helpful for Integration and System testing for a tester.  

  3. Build Link for all Test cases so the team can generate the reports.  

  1. Use shared steps if needed. Create a new one if needed.  

  1. Name of shared steps – Testcase name (Shared) 
     

  1. Manage the stage of testcases. Assign for peer review. 

  2. Mention any success / alert message, title & sub title, form labels in double quotes and italics 

  3. Mention verification Statement in bold   

  4. Mention expected result for each steps as per need of spec

  5. Mention time estimates a test case if possible 

  6. Use keywords “Navigate” for page/ screen navigation  

  7. Mention hardware actions as required for a test step 

  8. Mention “Manual Setup” or manual database intervention as bold letters 



Friday, February 3, 2017

Finding Real IP Address in Coldfusion / by passing proxy server / download server or any proxy server



this code will help to get real ip address through cgi variable in coldfusion

<cfif CGI.HTTP_X_Forwarded_For EQ "">
<cfset real_ipaddress = CGI.REMOTE_ADDR>
<cfelse>
<cfset real_ipaddress = CGI.HTTP_X_Forwarded_For>
</cfif>


Monday, January 30, 2017

pass comma separated values in CFQuery / listqualify single quoted values

select distinct ruleid from MyRulesWITH (NOLOCK)
where
fieldid in (<cfqueryparam value="#arguments.fields#" cfsqltype="cf_sql_varchar" list="true" />)

<cfif variables.scorecardIds neq "">
  and name in (#listqualify(variables.name,"'",",")#)
</cfif>