Manual + Automation Testing Certification
- Overview of Testing
- Why testing is required
- Cause of software defects
- Myth/fact about software testing
- Levels of testing- Unit, Integration and System Testing
- Key difference between Manual and Automation Testing
- Functional & Non-Functional Testing
- Requirement Analysis(RTM, feasibility report if applicable)
- Test Planning(Test Plan, Test Strategy )
- Test Case Development(Scenario, Test cases, Test Data, Review, RTM)
- Test Environment Setup
- Test Execution
- Test Cycle Closure
- Practical exposure of Test Management tools(Test Link/zephyr)
- Bug Life Cycle and Practical exposure of bug tracking tools(Jira/Bugzila)
- Waterfall model
- Brief introduction of Other SDLC model
- what is Agile and its variants
- Scrum Master, Product Owner and Team.
- Sprint, planning poker, Product backlog, planning meeting, scrum-meetings, Demo.
- Sprint velocity
- Burn down chart
- CI-tool brief(Build and Deploy)
- Release doc, Patch, RCA
- Overview of web-service/API testing
- Overview of XML/XSD and how used in testing
- Server/Application logs analysis and basic LINUX/UNIX command
- SQL basic queries example and assignments
- Overview of performance testing
- Challenges related to Real time testing and mitigation plan discussion
- Queries session
- Introduction to SQL
- Joining Tables
- Deleting Data
- Using Views
- Deleting Data
- Grouping Data
- Between Operator
- Overview of Selenium
- Java Setup
- eclipse setup
- why java for selenium
- First eclipse project
- First Java Program
- Installation of IDE
- Recording of script
- Running script
- RC introduction
- Overview of webdriver
- Drivers for FF.IE, Chrome
- Firepath and firebug addon installation
- Finding element using locators ID,xpath,link,CSS ..etc.
- Handling drop down
- Handling Alert
- Handling multiple windows
- Close and quite difference
- Open and navigate
- TESTNG and reporting
- Overview of webdriver 3.x
- Technical Assignments (8 Assignments)
- Aptitude Test Papers like (HCL, IBM, Wipro etc.)
- Resume Design By Dedicated Placement Cell
- Mockup Interview by Corporate Professionals
- Schedule Interview with valid reference in Software Companies
- Candidate Analysis (RCA), if candidate is not getting the job
- For B.Tech/MCA Industrial Training: Real Time Project based Training and projects for College Submission/Industrial Training Certificate.
Inquiry for Manual + Automation Testing Training
Please Find Software Testing Certification Course Duration
|Course Module||Course Duration|
|Software Testing Certification Course||5o (Hours)|
What is Automation Testing?
Software Automation Testing is a process of program verification in which the software is tested using basic functions such as running, execution, initialization, analysis and delivery of results. These are performed automatically using automation tools and it is one of the most necessary processes in software testing. It is quick, easy and reliable way to find out if any error in the functionality of the software is present. It is also a very cost effective method for software testing, which allows the company to develop trustworthy and durable software. Automation testing is one of the two types of software testing, the other being manual testing.
What is a framework?
A testing Framework or more precisely an Automation Testing Framework offers the basis of test automation and makes the process more effortless. The main advantage of a framework is to provide low cost of maintenance and offers flexibility in the entire process. It offers the user with several other benefits in the development, execution and reporting of the test scripts. Testing Framework is also a very coherent approach in software testing and plays a very important role in automation testing by providing a basic structure and a set of guidelines, which allow the user to achieve their desired results quickly.
What is basis for test case review?
The review of the test cases is usually based on the functional or program specification. A tester will write test cases on the basis of these features and while reviewing these test cases, the user will see that all the functionality is mentioned in the documents are covered in these cases. For unit test cases the review basis is program and functional specification and for integration and system test cases, SRS is the main base. Use cases and wireframes can also be used as a basis for writing test cases.
What all things can you automate?
There are many reasons for automation testing, which involves getting maximum returns on investment and reducing the development cycle by avoiding repetitive and cumbersome tasks and improving the quality of the software. Automation Testing is mainly performed on test cases in order to find out if those cases are performing as expected or having some kind of issues. However, there are things that need to be understood on by and when to automate. There are some things which may be automated, but It is wise to perform manual testing. Some of the things that you can automate in testing are:
- Continuous integration
- Graphic user interface
What are the different types of frameworks?
There are a total of 6 different types of UFT frameworks which are as follows:
- Linear automation framework: in this Framework, all the steps are written in sequential order and the user does not create any function.
- Functional decomposition/modular framework: software testers required to first identify the reusable code for automation and write the code in various functions.
- Business process testing framework: in this Framework, the test cases are divided into multiple scenarios and each scenario can be scripted using the business process component.
- Data-driven framework: in here the input data and input parameters or not coded in the test scripts.
- Keyword driven framework: the user can create multiple keywords, allowing the testers to associate unique actions or functions using the keywords.
- Hybrid framework: this is developed by combining various features of two or more testing frameworks.
What is Bug Life Cycle?
Bug life cycle refers to the journey of a bug from its detection to its closure in the developed program. The cycle starts when a software tester finds the defect and report it. The concerned team will then check the status of the bug and keep eye on several factors such as defect detection rate, defect reopens ratio, etc. It is then sent to the respective developer who works on the bug by opening assigning and validating the bug. At this time any error is resolved and the developer again opens the program to see if the bug still in the progress.
No posts were found.