Test Case

What is a Test Case?
“A test case has components that describes an input, action or event and an expected response, to determine if a feature of an application is working correctly.”

Levels:

There are levels in which each test case will fall in order to avoid duplication efforts.

• Level 1: In this level you will write the basic test cases from the available specification and user documentation. 
• Level 2: This is the practical stage in which writing test cases depend on actual functional and system flow of the application. 
• Level 3: This is the stage in which you will group some test cases and write a test procedure. Test procedure is nothing but a group of small test cases maximum of 10. 
• Level 4: Automation of the project. This will minimize human interaction with system and thus QA can focus on current updated functionalities to test rather than remaining busy with regression testing.

So you can observe a systematic growth from no testable item to a Automation suit.

Why we write Test Cases?
The basic objective of writing test cases is to validate the testing coverage of the application. If you are working in any CMMi company then you will strictly follow test cases standards. So writing test cases brings some sort of standardization and minimizes the ad-hoc approach in testing.

How to write Test Cases?
there are some fields to write test cases
1. Test Objective
2. Pre-conditions
3. Test data
4. Data base statemnts(SQL/Mysql/any)
5. Test Steps
6. Expected Result
using these feilds u can write but main thing u should understand the Requirement i mean u should under stand the whole Application wat u r going to test then only u can come to know the how to write steps n all.

Validation Testing Types

If the testers are involved in the software product right from the very beginning, then validation testing in software testing starts right after a component of the system has been developed. The different types of software validation testing are:

• Component Testing: Component testing is also known as unit testing. The aim of the tests carried out in this testing type is to search for defects in the software component. At the same time, it also verifies the functioning of the different software components, like modules, objects, classes, etc., which can be tested separately.

• Integration Testing: This is an important part of the software validation model, where the interaction between the different interfaces of the components is tested. Along with the interaction between the different parts of the system, the interaction of the system with the computer operating system, file system, hardware and any other software system it might interact with is also tested.

• System Testing: System testing, also known as functional and system testing is carried out when the entire software system is ready. The concern of this testing is to check the behavior of the whole system as defined by the scope of the project. The main concern of system testing is to verify the system against the specified requirements. While carrying out the tester is not concerned with the internals of the system, but checks if the system behaves as per expectations. 

• Acceptance Testing: Here the tester especially has to literally think like the client and test the software with respect to user needs, requirements and business processes and determine, whether the software can be handed over to the client. At this stage, often a client representative is also a part of the testing team, so that the client has confidence in the system. There are different types of acceptance testing:

• Operational Acceptance Testing
• Compliance Acceptance Testing
• Alpha Testing
• Beta Testing

Often when validation testing interview questions are asked, they revolve around the different types of validation testing. The difference between verification and validation is also a common software validation testing question. Some organizations may use different terms for some of the terms given in the article above. As far as possible, I have tried to accept the alternate names as well.

Difference between Verification & Validation?

Verifiaction:

• Means are we doing right thing.i.e we have to check whether we are implementing right process.  
• It is the examination of the process and checks r we building the product right? 
• It involves reviews and meetings to evaluate documents,plans,code,requirement and specification.
• This can be done with 
• checklist,
• Issues lists and 
• Walkthroughs.

Validation:Means are we doing things right.i.e we have to check whether we have developed a software as per the client requirement.

SAP Introduction

• SAP is an ERP Software where SAP stands for Systems, Applications and Products in data processing. 
• SAP was developed by German software company SAP AG in 1972 and the initial version was called SAP R/1. 
• In 1979, SAP launched SAP R/2 and in 1981, 
• New version called SAP R/3 was launched.

Advantages:

• Integration
• Efficiency
• Cost reduction
• Less personnel
• Accuracy

Disadvantages:    

• Expensive
• Not very flexible  

SAP's solution includes a number of functional modules, which support transactions to execute key business processes, such as:

• Financial Accounting (FI)
  • General Ledger (FI-GL)
  • Accounts Payable (FI-AP)
  • Accounts Receivable (FI-AR)
  • Bank Accounting (FI-BL)
  • Asset Accounting (FI-AA)
  • Funds Management (FI-FM)
  • Travel Management (FI-TV)
  • Special Purpose Ledger (FI-SL) (I am not sure this is really considered a module anymore)

   
• Financial Supply Chain Management (FSCM)
  • Credit Management
  • Cash and Liquidity Management
  • Collections Management
  • Dispute Management
  • Treasury and Risk Management

   
• Controlling (CO)
• Materials Management (MM)
• Sales and Distribution (SD)
• Logistics Execution (LE)
• Production Planning (PP)
• Quality Management (QM)
• Plant Maintenance (PM)
• Project System (PS)
• Human Resources (HR)