Tech Notes

An approach for testing an application is dependent on many factors and domain / industry type is one of them. Why? Because it helps in enumerating critical risks associated with an application, which can’t be ignored. For example, in healthcare, the most important aspect of testing is in safety of patients and compliance with government regulations. Listed below are tips and pointers to consider while testing the healthcare provider application(s). Introduction to Health Care Domain / Industry Healthcare Compliance & Regulatory Environment Healthcare compliance and regulatory environment are among the most complex to understand and apply. Most of these regulations are in place to ensure that hospitals protect the patient health records. This makes security testing utmost important for any healthcare applications. The the risk of violating the compliances is very risky a...

·          Opening/Creating different types of account viz. Saving and Checking (CASA) and Loan Accounts Etc ·          Cash/ Cheque Deposits using different services at Branch by Teller, and Cash Deposit Machines for (Self / Third Party) ·          Cash Withdrawal, Deposits, Transfers(between linked accounts) from ATM terminals ·          Low-volume (NEFT) and High-volume (Real time gross settlement systems - RTGS) transactions using different Banking channels (Like Internet Banking, Mobile, IVR Etc) ·          Automated Clearing House (ACH) and Electronic Funds Transfer (EFT) payments ·          Cash/ Liquidity Management function ·          Stop Cheque request, Utility Bill payments, Credit card...

Manual Testing Core Activities What are the core activities of testing especially for manual testers? How should we plan testing efforts? Most of the time, I have seen effort of review activities and retesting of defects are being ignored heavily and schedule get hit because of that. Following are the core test activities should be considered while planning - Test Ideas (Not Reviewed): Test idea is a test case with only summary and no details Test Ideas (Reviewed L1): Test ideas reviewed by peer team member Test Ideas (Reviewed L2): Test ideas reviewed by Test Lead / Test Manager Test Ideas (Signed-off): Test ideas reviewed by client and signed-off Test Cases (Not Reviewed): Test case is extension of test idea, putting more details around test idea (descriptive, detailed, Clear steps for execution, Test Data information etc.) Test Cases (Reviewed L1): Test cases reviewed by peer team member Test Cases (Reviewed L2): Test cases reviewed by test lead / test manager. Review...

As per defined in wikipedia – “A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code. Reports detailing bugs in a program are commonly known as bug reports, fault reports, problem reports, trouble reports, change requests, and so forth.” There might be many fields (information) need to be filled while reporting a bug.  The number of fields, mandatory fields, optional fields etc. differs from team to team.  But few bare minimum fields that are required during reporting a bug in almost all teams are as follows: Title Description Steps to Repro Expectation Severity / Priority Most of the time, testers go and try to provide these information in hurry,...

1.                Introduction The project is initiated as a pilot for the testing of [application]. [Provide information about the application in 3-4 lines] 2.                Application Details [Provide more details of the application including its feature set] 3.                   Technology Details [Technology being used in the application] 4.               Scope of Testing for the Pilot Project The following table defines the scope of testing of risks for the [application] Risk Based Testing - Test (Release x.x.x) Scope IS IS NOT -           Data Correctness / Quality -        ...