What is Keyword driven testing? What are base requirements for keyword driven testing?

Table driven testing, action word testing or key word driven testing, whatever you may call it, it is one and the same thing – a software testing methodology that has been especially designed for automated testing.

However, the approach followed by this testing methodology is quite different and involves dividing the test creation process in to 2 distinct phases namely:

1. Planning phase and the
2. Implementation phase

What is Keyword Driven Testing?

- It has been specially designed for automated testing.

- It does not mean that it cannot be employed for carrying out manual testing. - It can be very well used for manual testing as well. 

- The biggest advantage provided by the automated tests is of re-usability and so all this has eased up the maintenance of the tests that were developed at an abstraction level that was too high. 

- To say in simple words, one or more atomic test steps together form a key word.

- The first phase i.e., the planning phase involves the preparation of the testing tools and test resources. 

- The second phase i.e., the implementation phase depends up on the frame work or tool and thus differs accordingly. 

- Often a frame work is implemented by the automation engineers which has key words like enter and check. 

- This makes it easy for the test designers who do not have any knowledge of programming, to design the test cases based on such key words, that have already been defined by the engineers in planning phase that has already been implemented. 

- Such designed test cases are executed via a driver. 

- The purpose of this driver is to read the key word and execute the corresponding code.

- There are other testing methodologies which put everything right in to the implementation phase instead of performing the test designing and engineering separately.

- In such a case, the test automation is only confined to the test design.

- There are some keywords that are created using the tools which had the necessary code already written for them such as edit and check. 

- This helps in cutting down the extra number of engineers in the process of test automation. 

- This makes the implementation of the keyword a part of the tool. 

Advantages of Key word Driven Testing

There are some advantages of key word driven testing as stated below:

1. Concise test cases.
2. Test cases are readable only by the stake holders.
3. Easily modifiable test cases.
4. Easy reuse of the existing keywords by the new test cases.
5. Keywords can be re used simultaneously across multiple test cases.
6. Independent of programming languages as well as specific tool.
7. Labor gets divided.
8. Less requirement of tool and programming skills.
9. Lower domain skills required for keyword implementation.
10. Layer abstraction.

Disadvantages of Keyword Driven Testing

1.   A longer time is required for marketing when compared to manual testing.

2.   Initially, high learning curve.

Base Requirements of Key word driven Testing

1. Full separation of test development and test automation processes: The separation of these two processes is very much required for test automation since both of them have very different skill requirements. The fundamental idea behind this is that the testers should not be programmers. Testers should have the ability of defining test cases which can be implemented without having to bother about the underlying technology.
2. The scope of the test cases must be clear and differentiated: The test cases must not deviate from their scope.
3. Right level of abstraction must be used for writing the tests: Tests must be written at levels such as lower user interface, higher business level etc. 

What is meant by Function Generator in WinRunner?

With the aid of visual programming it has been possible to add the TSL statements to the test scripts. Whenever a test is recorded, TSL statements in the test script are generated by the winrunner whenever a user interaction takes place like some input is supplied from the key board or a GUI object is clicked. 

Apart from the record-able functions, TSL comes with many other powerful functions that add considerable flexibility to your test scripts. These functions can be added to the test scripts with the help of the function generator which is the winrunner’s only visual programming tool. 

The function generator is actually an error free and a quick way to obtain good program scripts. 

Tasks carried out by Function Generator

With the help of the function generator the following tasks can be carried out:

1. It helps you in adding the context sensitive functions which help in obtaining information from the software system or application that is being tested and performing operations on the GUI objects.

2. With the help of function generator you can even add some analog as well as standard functions for performing the tasks that are non context sensitive like for example, appending some user defined messages to the test report or doing synchronization of the test execution.

3. Customization functions can be added that help in the modification of the winrunner in accordance with the testing environment. 

Functions are added by the function generator in form of TSL statements. These TSL statements are added in either of the two following ways:

1. By choosing a function from the list: This is the default way of adding functions. A default function is suggested by the winrunner for the GUI object that has been pointed to. Usually the added function is the one that retrieves information or is a get function.

2. By pointing to a GUI object: This is the advance method and should be used by experts as recommended. First, the insert function command is chosen by the user and a GUI object is pointed. Instantly an appropriate context sensitive function is suggested by the winrunner and values are also assigned to its arguments by the winrunner itself. The function suggested by the winrunner can either be modified along with its arguments or a different function can be chosen to replace it. 

More about Function Generator...

- Once the TSL statements to be added have been generated, they can be either pasted in to the test script or can be executed using the function generator. 

- Function generator can be customized in order to make an account for the user defined functions that are quite frequently used in the test scripts. 

- Function generator can be further enhanced by adding to it many other new functions, categories as well as sub categories. 

- For every new category that is added, a default function can be set and also an already existing default function can be changed. 

- Before generating a function for a GUI object, it is thoroughly examined by the winrunner. 

- After determining its class, an appropriate function for that particular object is suggested by the winrunner. 

- This suggested default function can either be accepted or rejected and if rejected a new one can be picked up from the list. 

- For selecting a non default function for the GUI object you need to go to the insert menu, selection function option, then select the option “for object/ window” or you can simply click the insert function for object/ window button present on the user tool bar. 

- Point to the GUI object you wish to be affected and left click. 

- A function generator dialogue box appears, click change option in it.  

What are different types of running a test in WinRunner?

After you are done with the creation of the test scripts for your cases, you subject them to be compiled by the winrunner which in turn interprets these test scripts line by line. Ultimately, the tests are executed as though they were being run by a real world human user. 

In this article we are going to discuss about different types of running a test in winrunner. 

1. Running a test to check the software system or application:  

This type of test run involves a rigorous check of the behavior of the software   system or application as well as a sincere comparison among the current results and the expected results. The folder where you want the verification results to be saved can be specified by you itself. Following steps are followed for this type of test run:

a)   For opening your test hog down to open option in the file menu and click it to open a test.

b)   But be first make it sure that you have set the run mode to verify run mode on the test tool bar.

c)   Now choose an appropriate test menu command or you simply click on one of the run options. When you do this a run test dialogue box appears.

d)   It is your wish if you want to save your test results with a default test run name.

e)   The winrunner saves the test results.

    2. Running a test for debugging a test script: 

   Whenever you have to debug the test scripts a similar type of comparison is carried out by the winrunner as in the previous type between the current response and the expected response. After debugging only one set of debug results is saved in the debug results folder. So whenever you carry out a second execution of the same test, the results are over written by the winrunner. Following steps can be carried out for this type of test run:

    a)   Follow the same step a in the previous test run type to open a test.

    b)   Then go for the debug option from the list of run modes on the test tool bar.

    c)   Then you go for the run or debug menu command that you want.

    d)   For executing the entire test go for the “run from top” option available in the test menu.

    3. Running a test for updating the expected result: 

    This type of test run helps one in updating the expected results. In this case, the expected results that were created earlier are replaced by the new results and these new results in turn become the subject of comparison for the subsequent test results to come. For running a test for updating the expected results follow the first step as given in the previous two cases for opening a test. Go to the list of run modes from the test tool bar and select the update option. Then choose an appropriate test menu command from the list. For updating the entire set go for the option “run from top” in the test tool bar or simply click on the “from top” button on the tool bar.

    4. Running a test for checking the date operations: 

   Once a test has been created that checks date operations, it is run to check in what way the software system or application responds to the date information present in the test. You must make sure that in the general category of the options dialogue box the option “enable date operations” must have been selected. 

How will you synchronize tests using WinRunner? When should you synchronize? What are Synchronize settings?

Whenever a data driven test is created the fixed values of the test script language or TSL statements are parameterized. Contrary to all this there are no fixed values in the synchronization points.

Instead they consist of the following:

1. A bit map check point statement/ bit map synchronization point statement: It contains a reference to the stored bitmap.
2. A GUI check point statement: It contains a reference to a stored check list and expected results.

You should always remember this point that it is always better to create a single property check rather than creating a GUI check point while checking the properties of the GUI objects during a data driven test. This is recommended since a single property check does not consist of a check list and hence it is quite easy to parameterize. 

In this article we answer the following three important questions regarding synchronization in winrunner:

1. How will you synchronize the tests using the winrunner?
2. When should you synchronize?
3. Synchronization settings

How to synchronize?

- First step in the synchronization of the tests is the creation of an initial test by either programming or by recording. 

- Next step, will be to use the data driver wizard. 

- Go to the table menu and select the option data driver wizard. 

- The purpose of the data driver wizard is to convert your test scripts in to a data driven test and to parameterize the data values. 

- The third step will involve the creation of column in the data table for all the synchronization points and check points whose values are to be parameterized. - Then you should enter dummy values in every row and column but all the dummy values should be unique from each other. 

- Fourth step is to open up the assign parameter dialogue box from the table menu. 

- Then you should change the expected values of the synchronization points and check points to be used from the data table. 

- Now fifth and the final step involves running your tests in update mode by selecting update mode from the run mode box. 

- Give the run command to run your tests and while the test is running the winrunner will be reading the expected values from the data table. 

- But since you have changed the expected values, Winrunner will not be able to find these and thus will recapture the values from the application software and save them as the expected values. 

- Later, you can run the same tests in verify mode for verification of the behaviour of your software system or application.

When should we synchronize the tests?

- Whenever you feel that there your software system or application is showing some inconsistencies in its performance or behaviour, you can synchronize the tests as it will compensate for these inconsistencies in your application during a test run. 

- When you introduce a synchronization point in the test scripts you are instructing your winrunner to suspend the current test run and continue the test after getting a cue.

Synchronization Settings

- Winrunner offers many testing options like delay_msec, min_diff and timeout_msec. 

- These testing options can be modified using appropriate synchronization settings.

- These testing options can be set globally by using the below mentioned corresponding options:

1. Time out for check points and CS statements
2. Delay for window synchronization and
3. Threshold for difference between bitmaps

- You can get these options by going to the general options dialogue box, the selecting run, then settings, then run and then selecting synchronization categories. 

What is the difference between winrunner and test director?

The winrunner is often confused with the test director. But both of them have considerable differences between them. In this article we shall explore the differences between the winrunner and the test director. We shall list all the differences below:

Difference #1:

The winrunner is an automated testing tool that was developed as a functional testing tool by the HP (hewett Packard) whereas the test director is a test management tool. The former tool tests the software system or application while the latter one manages all those tests that are to be performed.

Difference #2:

The winrunner tool only helps in carrying out the tests on the software systems and applications whereas the test director organizes the whole test process as it name says the “test director” much in the way that a film director directs the shoot of the movie. In some cases the test director has also helped in the creation of the test cases.

Difference #3:

Winrunner is a tool that serves the purpose of the automated testing and is mostly used whenever the testers have to carry out any one of them:

a)   Regression testing or

b)   GUI testing

One plus point of the winrunner is that the testing carried out with its aid is quite efficient, fast and reliable. On the other hand the test director is a web based tool for the purpose of management of the tests. In test director, the management of the following takes place with the use of a centralized data base:

    a)   Requirements documentation

    b)   Specification documentation

    c)   Test plans

    d)   Test cases

    e)   Defect managing and

    f)    Defect tracking etc.

Both are completely different tools that have been developed by the same pioneer mercury interactive.

Difference #4:

One of the fact about winrunner is that it can only create automated test scripts and does not has the ability to handle the already automated test scripts. On the contrary, the test director or TD (as you say) forms a kind of central repository for storing the information related to bugs and their management.

Difference #5:

It won’t be wrong to call the winrunner a regression testing tool or a record and play back tool whereas the test director being a test management tool can even help you in the execution of the pre- automated test scripts through a special environment called test director environment.

Difference #6:

The speciality of the winrunner lies in automation of the scripts whereas the test director excels in the field of defect tracking and management.

Difference #7:

Winrunner is used for the following:

a)   Complex Functional testing

b)   Complex Regression testing and

c)   Automating the test scripts

The test director is used for the following purposes:

         a)   Creating the test plans

         b)   Preparing the test cases

         c)   Executing the test cases

         d)   Generating the bug reports

         e)   Maintaining the test scripts and so on. 

Difference #8:

The winrunner is a testing tool that has eased the complexity which is faced by many of the testers during regression testing. On the other hand the test director is a management tool holds the responsibility for keeping a perfect and clean record of the software testing process right from the requirements phase to the end of the testing phase.

Difference #9:

With the help of winrunner the TSL scripts can be recorded and updated and replayed a number of times as and when required whereas with the aid of the test director one can even run the winrunner as well as loadrunner scripts on a remote computer system. 

How do you plan test automation? Can test automation improve test effectiveness?

“How to plan test automation?” is perhaps the most frequently asked question of today’s software testing field. Another important question is, “can test automation improve test effectiveness?” 

In this article we have tried our level best to answer both of these questions! 

What is meant by Test Automation?

- In test automation, we actually develop a quick process that will take care of the execution of the tests by itself i.e., without any human intervention.

- It also compares the actual and predicted outcomes, sets up the pre- conditions for the tests.

- A common test automation process involves automation of a manual testing process that makes use of a formalized testing tool. 

- Although the manual testing can discover a whole lot of defects in the software system or application, it is quite laborious or you can say it involves a lot of drudgery and time.

- It is not possible for you to discover defects of all the classes using manual testing; it is a task that can only be accomplished using test automation. 

- Test automation takes time only once i.e., while you automate them and after this it saves a whole lot of time when compared to manual testing, tests can be run quickly and repeatedly. 

How to plan test automation?

There are two approaches to test automation and both of them are equally good and either of them can be followed. They are:

1. Code driven testing: This approach involves public interfaces to classes, libraries or modules to be tested with a whole variety of the input arguments for the validation of the results that are returned and are quite correct.

2. Graphical user interface testing: This approach involves a testing frame work that generates a user interface events like mouse clicks and key strokes for the validation of the observable behavior of the program i.e., whether it is correct or not?

There is one drawback which is that the test automation tools can cost you much and they cannot be employed without manual testing. Test automation is effective if you have to repeatedly test one thing. 

There is one more approach to the test automation which is commonly known as “model based testing”. 

- Using this approach you automatically generate tests through the use of a model of the software system or application for the generation of test case but this method of planning test automation is still under research and controversies. 

- One should keep the following questions in mind while planning the test automation:

1. What to automate?

2. When to automate?

3. Whether or not automation is really required?

Can Test Automation improve Test Effectiveness?

Yes, test automation can improve test effectiveness.

- The test cases generated by test automation are quite reliable as compared to those created by manual testing.

- In test automation, human error is eliminated.

- The tests generated are repeatable as well as programmable. 

- They also have the following characteristics:

* Reusable

* Comprehensive: The test suite that is built covers all the features of the software system or application.

* Cost reduction: Due to less resources, used cost is also reduced.

* Fast: Testing is quite fast.

* Better quality software: The resultant software system or application is of better quality since it is tested by a large number of tests with fewer resources and less time.

Describe some automation testing tools?

Automated testing has greatly reduced the drudgery of the developers who otherwise would have to carry out testing on big software systems and applications projects manually. Today there are many automation testing tools available to your advantage. Using these tools you can automate any of the test scripts which will make your work easier than ever consuming less time and efforts. In this article we have discussed about some of the automation testing tools. They are as follows:

1. TestComplete: 

- This testing tool has been designed for both the novice as well as advance testers.

- Using this tool, creating, managing and running tests for any system becomes so easy be it a desk top or web software. 

- It has got a quite easy to use interface and a whole lot of tools for the purpose of customizing it

- This tool supports cross browser web testing, html5 applications and distributed testing as well. 

- Using this tool, you can create tests using just one browser which can be run on almost any browser.

- You do not have to make any changes to the tests i.e., testing is completely browser independent. 

- Furthermore, this testing tool is independent of any other development tool or software application. 

- It supports all the languages.

2. Telerik by Test Studio: 

- This testing tool supports functional testing, load testing, performance testing, and mobile testing very well. 

- It also supports in depth desk top testing i.e., you can easily test AJAX, HTML5, WPF and Silverlight apps. 

- This tool is quite affordable.

- Using this tool, you can create as well as capture tests.

-Web performance tests can also be created which offer a detailed insight in to the performance metrics of your apps.

- This tool is quite advanced and covers most of the technologies and protocols. 

- Using this tool, you can even run a functional test which in turn can help you to gather data on server processing time, client rendering time and network latency etc. 

- Furthermore, this tool supports testing for iOS apps.

- It also provides support for iphone, ipad, ipod, test natives, web and hybrid apps etc.

3. Micro focus- SilkTest: 

- Using this tool, one can create robust, powerful and fast automated tests across a quite broad range of technologies and applications. 

- It can be used easily for the identification of the quality related problems that occur in the early stages of the SDLC or software development life cycle. 

- Till now two versions of this testing tool have proven to be quite worthy namely Silk4Net and Silk4J.

- These two testing tools provide you with the option of bringing the power of SilkTest to integrated development environment of your choice like eclipse or visual studio and so on. 

- This testing tool has showed quite lot robustness.

4. HP: Unified Functional Testing Software (quick professional tool): 

- This tool rules the software industry.

- This tool has got the ability of accelerating the functional testing by following a simplification process for simplifying the test design and maintaining both the non GUI based applications and GUI based applications.

- The integrated test scenarios can be validated quite easily.

- All these features result in a reduction in risk and improve the quality for the applications of the modern era. 

- This testing tool includes HP service test products and HP functional testing. 

- It also includes some of the other add-ins from HP. 

- Using this tool you can increase the efficiency of your testing by using the automated processes and re- using of the data. 

What are different automated testing challenges?

Automated testing though being a modern testing methodology, faces challenges. Test automation is used whenever a large number of test cases are to be executed. A huge number of test cases cannot be executed manually.

AUTOMATED TESTING
- In automated testing, an automation tool or software is employed to handle the execution of the test cases.
- Such software even compares the actual outcome to the expected outcome.
- It efficiently generates the test data and also the preconditions.

MANUAL AND AUTOMATED TESTING
- Test automation process is mainly used to automate a manual testing process which is typically a much formalized one.
- Although manual testing is way more effective than the automated testing, it consumes too much of time and requires a larger effort.
- Though, manual testing is able to discover more errors and bugs, there are certain kinds of bugs that cannot be discovered up by manual testing.
- For automated testing a computer program is written that will take up the whole testing process which otherwise would have required manual work.
- Manual testing sounds like quite a drudgery! Isn’t it?
- Once the automated software is ready, the test cases can be executed quickly and can also be repeated any number of times without much fuss.
- Automated testing proves to be time, efforts and cost effective method for the software projects that are way too lengthy and need more maintenance.

CHALLENGES FACED IN AUTOMATED TESTING
Test automation tools are expensive and therefore they are employed in certain definite combinations with the manual testing. There are few challenges faced in automated testing:

1. COST EFFECTIVE
One of the challenges that automated testing faces is that it becomes cost effective only when used in the long term i.e., for regression testing of a software system or application.

2. Requirements
- The requirements for a software system or application are identified from the user stories.
- User stories are basically a description like of the software product.
- These requirements are sorted according to the priority as follows:

(a) High priority Requirements
These are the most critical requirements of a software system or application and have to be included in to the software before it is released to the public.
(b) Medium priority Requirements
These requirements are not so critical to the software system or application and hence can be worked around later. But, it should be done before the implementation.
(c) Low priority Requirements
These requirements are added just to enhance the overall quality of the software system or application. But, the software can do without these requirements.

After sorting up on the requirements in the order of their priority, the iterations for the release are planned and each iteration release takes about 1-2 months. Meanwhile too much of change occurs in the requirements of the software. Many a times such changes cause the iterations to bump. This is indeed a great challenge that hinders the implementation of the automating processes.

3. Tools
- The traditional tools don’t seem to work for all kinds of automated testing processes.
- For example, the traditional tools cannot be used for the agile automation process since they are capable of solving only the traditional problems.
- This makes it difficult to implement the automation in the early stages of the testing cycle.
- The deployment of the automated testing processes become simpler only after the whole software comes to the verge of completion since by then many issues had been settled.
- So, making a wise selection of tools is crucial for the automation and also poses a big challenge.

4. Effective resource management as the program grows poses another problem.
5. Lack of effective communication among the team members.

What is the difference between scripted testing and exploratory testing?

Though exploratory testing and scripted are considered being a part of each other, there is a lot of difference between the two.

The scripted testing is performed by a set of test scripts which can be defined as a set of instructions that are to be performed on the software system or application under the test to test a particular functionality as required.

There are following ways of executing test scripts:

1. Automated testing:
- It can be easily repeated and is faster than manual testing.
- It is very useful when it is required to run the same tests over and over again.
- It is performed as a part of regression testing.
- Automated tests are poorly written and they may break during the execution.
- They only test what has been programmed into them.
- They only ensure that old bugs do not reappear.
- Manual testing and automated testing should be mixed together and used for exploratory testing.

2. Manual testing:
- This is the oldest and the most rigorous forms of testing.
- The test cases are reviewed by the whole testing team before using them.
- The test cases are either created at the basic functionality level or at the scenario level.

3. Short programs or test scripts written in a programming language (C#, C++, expect, TCL, java, Perl, PHP, python, power shell) or a special automated functional GUI test tool (like Borland silk test, HP quick professional test, rational robot etc) can be used to test functionality of a software system or application.

4. Short programs that have been extensively parameterized or data driven testing.

5. Table driven testing or keyword driven testing i.e., using reusable tests created in a table.

CHARACTERISTICS OF SCRIPTED TESTING
- Scripted testing is considered to be as a waste of resources by most of the testers.

- According to them the scripted manual testing inhibits the mind of the tester to use their creativity.

- Also, this testing requires heavy documentation as well as considerable amount of resources to create them.

- They often get out dated since the changes in the system are inevitable.

- Though being so criticized manual scripted testing is used by many organizations.

- The test cases are made repeatable and easy enough for a tester to perform testing with minimum supervision.

- Manual scripted testing is used in contracts where contractual agreement states that written requirements and specifications of the software must be met.

- Scripted test cases are useful where the tests are used as benchmark and have to be executed in the same way, every time.

CHARACTERISTICS OF EXPLORATORY TESTING
- In contrast to scripted testing, exploratory testing is a usual approach to software testing and can be defined as a test designing, test execution and simultaneously learning process.

- Exploratory testing is a kind of software testing that is emphasized and focused up on the responsibility and the personal freedom of the software tester.

- Exploratory testing is a kind of software testing that is emphasized and focused up to optimize the quality and effectiveness of his /her work continually by taking in to consideration mutually supportive activities like test designing, test related learning, test result interpretation and test execution.

- The activities run in parallel to each other.

- Exploratory testing basically heeds to exploiting the creativity of the tester or the programmer.

- During the testing of the software, the tester comes across various new things to learn together with experiencing them.

- Exploratory testing can be thought of as a black box testing methodology or technique instead of thinking of it as an approach to testing that can be used for any type of testing methodology and also at any phase of development of the software system or application.

What is the difference between automated testing and manual testing?

Automated scripted testing and manual scripted are two most common and popular ways of carrying out the scripted testing. Scripted testing is performed by a set of test scripts which can be defined as a set of instructions that are to be performed on the software system or application under the test to test a particular functionality as required.

Automated testing is mostly used.
- In automated testing the test cases are executed automatically and there is no need of human intervention.

- Non- requirement of human intervention is the best advantage of automated testing.

- It can be easily repeated and is faster than manual testing.

- It is very useful when it is required to run the same tests over and over again.

- It is performed as a part of regression testing.

- The main drawback of automated testing is that the automated tests are poorly written and they may break down or crash during the execution.

- They only test what has been programmed into them.

- They only ensure that old bugs do not reappear and don’t prove to be a good methodology to find out new bugs and errors.

In contrast to automated testing the manual scripted testing is the oldest and most rigorous form of software and application testing.
- In manual testing the test cases are reviewed by the whole testing team before putting them in to execution.

- These test cases are created at two levels.

- The first level is basic functionality level and the second one is the scenario level.

- Apart from reviewing of test cases, the designing is also done by the whole software development team.

- Manual scripted testing is considered to be a waste of resources by most of the testers.

- According to some testers the scripted manual testing inhibits the mind of the tester to use their creativity and also this testing requires heavy documentation as well as considerable amount of resources to create them.

- They often get out dated since the changes in the system are inevitable.

- Though being so criticized manual scripted testing is used by many organizations.

- The test cases are made repeatable and easy enough for a tester to perform testing with minimum supervision.

- Manual scripted testing is used in contracts where contractual agreement states that written requirements and specifications of the software must be met.

- Scripted test cases are useful where the tests are used for the benchmarking purpose and have to be executed in the same way, every time.

- The testers should have a strong knowledge of the software system or application since in manual scripted testing; the test cases are created beforehand.

- The primary sources of information to the testers are functional design specifications, requirements documents etc and so on.

- To make the testing more effective, the testers are free to use supplementary sources of information to increase their knowledge of the software system or application by rigorous discussions with the development team.

- Manual scripted testing is used in situations or programs where a waterfall methodology along with the V-Model has been implemented.

- Apart from waterfall and v model methodology, this approach can also be used for projects where requirements and specifications are frozen and likelihood of modifications in those requirements and specifications is very less and this is also suitable for the situations where safety and regulatory situations demand proof of testing.

- Generally, this manual testing approach is considered old but, it is quite relevant in this current era of market driven applications.

The best methodology is mixing manual testing and automated testing together and using it for exploratory testing.