Manual Testing Course Curriculum

 Manual Testing Course Curriculum

   Introduction

• What is Testing

• What is Quality

   Software Development Life Cycle

• Initial Requirement phase

• Analysis phase

• Design phase

• Coding phase

• Testing phase

• Delivery and Maintenance phase

   Where Exactly Testing is used

• Conventional Testing

• Unconventional Testing

   Testing Methodology

• Black Box Testing

• White Box Testing

• Gray Box Testing

    Testing Levels

• Unit Level Testing

• Module Level Testing

• Integration Level Testing

• System Level Testing

• User Acceptance Level Testing

    Software Development Models

• Waterfall Model

• Prototype Model

• Evolutionary Model

• Spiral Model

• Fish Model

• V-Model

• Agile Model

    Development Architectures

• One Tier Architectures

• Two Tier Architectures

• Three Tier Architecture

• N-Tier Architecture

    Type of Testing

• Build Verification Testing

• Regression Testing

• Re-Testing

• Alpha Testing

• Beta Testing

• Static Testing

• Dynamic Testing

• Installation Testing

• Compatibility Testing

• Monkey Testing

• Usability Testing

• End-To-Testing

• Exploratory Testing

• Security Testing

• Port Testing

• Reliability Testing

• Adhoc Testing

    Software Testing Life Cycle

• Test Planing

• Test Case Design Techniques

• BVA, ECP, Decision Table Testing, State

• Transaction Testing and Use Case Testing

• Test Development

• Prepare RTM

• Test Execution

• Result Analysis

• Bug Tracking and Reporting

• Test Closure Activity

Manual Testing Introduction

Manual Testing

• Test Complete gives you an opportunity to create and manage manual tests when testing your application. This kind of testing allows creating a collection of steps to be performed manually when the application is being tested, with a description of and detailed instructions for each step. A tester carries out these instructions manually and indicates whether a particular step was performed successfully or not. Manual testing is usually performed at the initial stage of software development, when automated tests are not effective yet due to the fact that the software and its user interface are not stable enough and may be modified a lot.

• Also, Test Complete provides an ability to perform keyword tests as manual test steps so that some keyword test operations can be automatically executed during the manual test run. This allows you to automatically perform some helper actions that are not necessary to be done manually during the manual test run. This can be helpful at the intermediate stage of software development, when some functionality of the application is quite stable and can be tested automatically (for instance, using keyword tests), while manual testing is still more applicable for other features of the application. In such situations, combining keyword tests with manual tests is quite effective and may save a lot of your time. For more information on this, see Using Keyword Tests in Manual Tests.

• When a manual test is running in Test Complete, the Step Description dialog describing the current test step is shown on the screen. This dialog holds instructions the tester should perform manually in the current step. The dialog allows the tester to stop testing or indicate whether the step was accomplished successfully or whether it failed. After the testing is finished, you can see results of each step in the log.

• Besides that, Test Complete allows managing manual tests from scripts and keyword tests. This opportunity is implemented with the help of the Manual Testing program object. Test Complete also provides a number of events which you can use to perform specific actions on each step of a manual test, on test finish and on specifying the test result (fail or success).