FacebookTwitter    Contact Us | Login

Training in Quality Assurance (QA), Manual Testing, HP QTP Certification, QA Tools, QA Integrated, BA Integrated, ISTQB, Business Analysis, BA, QA+BA Integrated, Health Care BA, SAP testing, SAP Basis, Oracle 11i Financials, Oracle R12 Financials, Oracle Business Intelligence Enterprise Edition, Java / J2EE, Advanced Java, Core + Advanced Java / J2EE, ASP.Net, Sharepoint, SAS, Health Care Domain For QA-BA

Re-testing and Regression Testing

Whenever any bug is fixed, two forms of testing is done on the fixed part. One is the Re-testing and the other is the regression testing. Let us see what’s the difference between these two testing types.   Re-testing: ISTQB Definition of Re-testing: Testing that runs test cases that failed the last time they were run, in order to verify the success of corrective actions. Once a defect is detected and fixed, it is necessary to confirm that the problem has been successfully removed. This is called as re-testing or confirmation testing. In Re-testing, it is important to ensure that the test is executed in the same way as it was the first time , using the same inputs, data, and environment. Automation testing tools can be useful in this type of testing work. But, it’s difficult to determine how much re-testing is needed especially near the end of development cycle. Re-testing...

Entry and Exit Criteria in Software Testing

In order to know when to start and when to stop the testing work, it is very much important to define the Entry and the Exit criteria for the success of any project.   Entry Criteria : Entry criteria is the minimum eligibility or the minimum set of conditions that should be met in order to start the testing work . Entry criteria are documented and signed off   during the test planning phase and is included in the relevant test plans. Typical entry criteria may include the following: All test hardware platforms must have been successfully installed , configured, and functioning properly. All the necessary documentation, design, and requirements information should be available that will allow testers to operate the system and judge the correct behavior. All the standard software  tools including the testing tools must have been successfully installed and functioning properly. All personnel involved in the testing effort must be trained in...

Severity and Priority levels in Software Testing

Priority: Priority is associated with scheduling which tells us the importance of the defect to solve with respect to customer. It indicates the urgency or importance of fixing a bug. Priority can be categorized into following levels (P1 as highest and P4 as lowest): Urgent (P1): Must be fixed in the next built. High(P2): Must be fixed in any of the upcoming builts but should be included in the release. Medium(P3): May be fixed after the release. Low(P4): May or may not be fixed at all.   Severity: Severity is associated with standards which tells us how bad the defect is and what impact it will have on the software application with respect to the customer requirement and on the user. The severity of the error is expressed as a number between one and four(1 being the highest and 4 being the lowest), and is defined as follows: 1 – An...

Verification and Validation Testing

For every software development life cycle, a part of testing is focused on verification testing and a part is focused on validation testing. Both these terms are frequently used in the software world but, the meaning of those words are mostly vague and debatable.  I have made an attempt here to state  the difference between these two terms as clearly as possible. Verification Testing: Verification is to see whether a work product/component/system meet the requirements set. In short, it focuses on the question” Is the deliverable built according to the specification?” Verification is static i.e the software is inspected looking into the code line by line or function by function without actually executing the code. So, here the code is just reviewed to expose any defects early in the life cycle. It typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done using checklists, inspections,...

Agile Development Model

The literal meaning of “agile” is about fast delivery of the software with more ease of development. This methodology mainly focuses on customer satisfaction by rapid, and continuous delivery of useful software.  This useful software is delivered frequently ( in weeks rather than months). Agile methods break the tasks into small increments with minimal planning, and do not involve any long term planning. These iterations are time boxed that lasts typically from one to four weeks. Each iteration involves a team working through a entire SDLC cycle ( from requirements, to design,  to coding,  to unit testing, and finally to acceptance testing). The working product is demonstrated to the stakeholders and, then the stakeholders produce documentation as required. The main goal of each iteration is not adding enough functionality to warrant a market release but, is to have an available release with minimal bugs at the end of each iteration.  Agile...
What is the importance of an Activity Diagram?

What is the importance of an Activity Diagram?

The main use of an activity diagram is to show the work flow of the business and to show the activities happening in the business system and actions completed. In a companies there may be different sections like medical, accounting, HR etc..and each department has different privileges to the system....
What are the types object Repositories in QTP

What are the types object Repositories in QTP

QTP supports 2 types of Object Repository, 1) Shared Object Repository (also called Global) 2) Per-Action Object Repository (also called Local) Per-Action Object Repository is used by default. The extension for Per-Action Object Repository is “.mtr”. Shared Object Repository is preferable while dealing with dynamic objects which are called in...
Latest entries

Introduction to Quality Assurance QA

This is a demo video of Quality Assurance ( QA ) online training offered by Yes-M Systems – IT consulting and Training Services Provider (visit http://www.myyesm.com for more information)  

Demo Session on Quality Assurance QA & Business Analysis BA Online Training

This is a demo video of Quality Assurance QA & Business Analysis BA Online Training offered by Yes-M Systems – IT consulting and Training Services Provider (visit http://www.myyesm.com for more information)  

Introduction to Business Analysis BA

This demo video gives an introduction to Business Analysis (BA) offered by Yes-M Systems – IT consulting and Training Services Provider (visit http://www.myyesm.com for more information)  

Business Analysis BA Concepts

This video talks about the concepts of Business Analysis BA  offered by Yes-M Systems – IT consulting and Training Services Provider (visit http://www.myyesm.com for more information)  

Syllabus of Quality Assurance (QA) & Business Analysis (BA)

This demo video talks about the syllabus of QA & BA online training offered by Yes-M Systems – IT consulting and Training Services Provider (visit http://www.myyesm.com for more information)  

Why does Automated Software Testing fail?

Automated software testing has plenty of benefits and a lot of challenges. Despite the availability of a broad array of tools for software automation – Silk Test, Selenium, HP QTP, Watir, etc. – almost every QA Testing teams struggle with the similar standard architecture issues. In my opinion most of the issues are due to...

What is the role of QA & QC?

QA: Process oriented testing QC: Product oreinted testing QA: Clears the defects QC: Detects the defect QA: Line function QC: Staff function