First half all a Tester should have Multi Talent …. He want to know all basic Testing types … I pasted some testing types I hope that will help for you… if the person have knowledge in Software engineering it’s very easy to learn testing … if you want know more details let me the same… thanks!
Types of Testing:
Testing can be done for checking the Functional areas in the website or for measuring he performance for each site with different loads. Please find below the list of testing to be performed for the STNG websites.
1. Integration Testing
2. Functional Testing
3. System Testing
4. Regression Testing
5. Smoke Testing
6. Stress Testing
7. Load Testing
8. User acceptance Testing
9. Other types (based on request).
In integration testing the separate modules will be tested together to expose faults in the interfaces and in the interaction between integrated components. Testing is usually black box as the code is not directly checked for errors. It is done using the integration test design prepared during the architecture design phase. Integration testing is generally conducted by software testers.
Functional testing will compare the system specifications against the actual system for any single module and not mainly done for the projects which are developed in multiple phases. Functional Testing will be automated using testing tools like Selenium, Badboy and Q.TP.
System testing will compare the system specifications against the actual system. The system test design is derived from the system design documents and is used in this phase. Sometimes system testing is automated using testing tools. Once all the modules are integrated several errors may arise. Testing done at this stage is called system testing.
Regression testing can be used not only for testing the correctness of a program, but it is also often used to track the quality of its output. For instance in the design of a compiler, regression testing should track the code size, simulation time and compilation time of the test suite cases. Regression testing plays a vital role in the Change Control phase where full System testing is not possible for all Change Requests.
Some testing is basically done to check whether the application smokes or not. Major Functional Test cases which are mostly Critical or Blockers can be used to run to check the stability for the application. This type testing is done mostly after the Code deployment in the Production environment.
Stress testing is a form of testing that is used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. Badboy and Jmeter can be used to check for this type of testing and it’s a part for Performance Testing.
Load testing is the process of creating demand on a system or device and measuring its response. When the load placed on the system is raised beyond normal usage patterns, in order to test the system's response at unusually high or peak loads, it is known as stress testing. The load is usually so great that error conditions are the expected result, although no clear boundary exists when an activity ceases to be a load test and becomes a stress test. Load testing is also a part for Performance Testing and Badboy and Jmeter will be used to check the Load for any system or STNG website.
User Acceptance Testing:
User Acceptance Testing (UAT) is a process to obtain confirmation by a Subject Matter Expert (SME), preferably the owner or client of the object under test, through trial or review, that the modification or addition meets mutually agreed-upon requirements. In software development, UAT is one of the final stages of a project and often occurs before a client or customer accepts the new system. Business Team from STNG will perform the UAT and based on the request the Testing team will assist them for completing the same.
Test Approach Model:
V model and Scrum model will be used for the Test Approach based on the project schedule and business needs.
Development Team Testing Team
Requirements Analysis Requirements Analysis
Project Plan Test Strategy, Evaluation & Test Plan
Coding/Development Test Case & Test Data prep
Bug Fixes-Functional Related Test execution-Functional
Bug Fixes-Performance related Test execution-Performance
Code Deployment Regression –Production env
User Acceptance Testing
V-Model is the commonly used Software Testing Life Cycle and it goes parallel with the development Team from the Requirements Phase to till the Release and Deployment.
Testing Team will involve in a detailed requirements study with the Subject Matter Experts/Business Team to understand the requirements in detail and their Business Needs.
Entry Criteria: List of requirements.
Exit criteria: Approved Requirements Document from the Business Team
Test Strategy, Evaluation and Test Plan:
Testing team will start working in this phase once the Requirements study is completed and will analyze the Strategy to be used by evaluating all the possible options for a feasible testing. Assumptions, Depen dencies and Constraints will be listed and added to the Strategy document and a detailed Test Plan will be prepared based on the Strategy document. The Test Plan will have detailed plan for each phase of testing and the resource utilized for the same.
Entry criteria: Requirements Document
Exit Criteria: Approved Test Strategy, Evaluation and Test Plan.
Test Case & Test Data Phase:
Detailed Test case and Test Data will be prepared for the project and areas to automate will be identified based on the effort required for regression and feasibility.
Test cases will be classified into Functional, GUI, Navigational and Destructive types .Test Data will be prepared for all the Test cases (exceptions will be dealt separately).
Automation Scripts will be generated for the Areas identified for both Automation and Performance using Selenium and Jmeter respectively. Babdboy will be used for both Automation-Functional and Automation-Performance.
Entry criteria: Approved Test Strategy, Evaluation and Test Plan
Exit Criteria: Completed Test case and Test data.
Test cases will be executed based on the priority and Functional test cases will be covered first in order to make the system stable. Automation scripts will be executed for all functional areas using Badboy or Selenium and bugs will be raised in Jira. Integration, Functional and System Testing will be done during this phase.
Entry Criteria: Signed off Test Cases and Test Data.
Exit Criteria: No Blocker or Critical bugs in Open Status.
Jmeter and Badboy scripts will be executed and bugs will be raised in Jira. Stress Testing will be performed at the beginning and the Stress Testing results will be used for the Load Testing to increase the increment of Load.
Entry Criteria: No Blocker or Critical defect/ bug in Functional and System Test cycle.
Exit Criteria: Performance results exceed the Baseline.
Regression test-Prod Environment:
Regression Test cases will be identified for execution –post deployment of code in Production. All the bugs raised during this phase will be raised in Jira and a separate email will be sent to the group. Release Notes will be prepared at the end of this phase and will have all the lessons learnt and major issues faced during the complete project life-cycle.
Entry Criteria: Successful deployment of code in Production, No defect or bug in Functional and System Test cycle.
Exit Criteria: No defect/bug in the Regression Cycle.
End-users and Business Team test the application or STNG website in order to check the application or website and the specifications given by them.
Entry Criteria: Successful deployment of code in Production, No defect or bug in Regression cycle.
Exit Criteria: Project Implementation Notes to the group.
hi parasss np first give one website to them and say find the bugs in tht site manually...notice how they are thinking .... for eg : In phone number textbox field if user types character means that is a bug ...
Some tips in traing the candidates,
If the candidate is Fresher, then we should make him understand the Basic concepts of testing (Terminologies) first. If he is strong in basics then ask him to test any website and post issues to know his logical skill or his Perception.
In case if you are dealing with Web based applications, ask him to go through the related sites to update his knowledge in understanding the core functionality of the applications.
Ask him to write the test cases by going through the Requirements or any clone sites so that he can get experience in writing test cases as well as in understanding the functionality very well.
It also depends on the type of projects. In case if you are handling Domain based application then we need to provide documents related to it and ask him to go through the documents to become expertise in the specified domain.
We should conduct Meetings with him regularly to track his skill and we need to motivate him.
If the candidate is Experienced and good in basics then we no need to give training ij basics. Just we need to know about the type of projects he handled and should train him (Eg: If he had experience in Web based applications and now we need to test Stand alone applications then we need to mold him in handling Stand alone applications).
We can provide him with the Issue Reports of the previous projects and ask him to analyze it so that he can test accordingly.
Qualities for Best Test Engineer:
1. Should have Degree Qualification (prefer science/engineering)
2. Should having good technical skills
3. Good communication skills
4. Good knowledge in Manual testing (testing process/testing types/testing techniques)
5. Exposer in Automation tools (Winrunner/QTP)
6. If you are looking for Automation Test Engineer, prefer should having experience in any automation tools
Hope above mentioned points are correct. Clarify me.
Skill Set Visualisation for Recruitment at Software Engineering Job Positions is not a standard set of formula.
It depends on Varying Levels of Autonomy and Responsibility,Size of organisation,Type of project
on hand, Methods of Testing employed etc...
_________ JAY ________.