Allocating Adequate Time for Software Testing: Ensuring Quality in Development

Introduction

In the realm of software development, testing is not merely a phase but a pivotal process that ensures the delivery of a high-quality product. Despite its significance, testing often faces challenges related to time allocation and resource management. This article delves into the necessity of allocating adequate time for testing, the common hurdles encountered, and strategies to enhance the testing process.

---

The Important Role of Testing in Software Development

Every software application, regardless of its complexity, is susceptible to defects. Even seasoned developers acknowledge the inevitability of bugs during the coding process. Recognizing this, effective testing becomes indispensable to identify and rectify these issues before the software reaches the end-user.

High-quality software is characterized by its reliability, efficiency, and user-friendliness. Achieving this standard necessitates a thorough testing process that uncovers and addresses defects, ensuring the software performs as intended under various conditions.

---

Challenges in Allocating Time for Testing

One of the predominant challenges in software projects is ensuring sufficient time is allocated for testing. Project managers and stakeholders often face pressure to expedite development cycles, leading to compressed testing schedules. This haste can compromise the thoroughness of testing, potentially allowing defects to persist into the final product.

Moreover, testing teams frequently encounter skepticism regarding their time estimates. This skepticism often stems from a lack of understanding of the testing process, especially among decision-makers without a background in quality assurance. Consequently, testing teams may feel compelled to reduce their estimated timelines, potentially undermining the effectiveness of the testing process.

---

Strategies for Effective Testing Time Estimation

Accurate estimation of testing time is crucial for project planning and execution. Here are some strategies to enhance the estimation process:

1. Leverage Experienced Testers

Seasoned testers bring invaluable insights into the estimation process. By reviewing project requirements, even at a high level, experienced testers can provide informed estimates based on their familiarity with similar projects and potential complexities.

2. Analyze Historical Data

Organizations can benefit from analyzing data from previous projects. By examining the testing timelines and challenges of similar past projects, teams can make more informed estimates for current endeavors.

3. Develop Detailed Test Plans

Creating comprehensive test plans based on available requirements allows for a more accurate estimation of the testing effort. These plans serve as a foundation for identifying necessary resources and timelines.

4. Conduct Rigorous Reviews

Subjecting test plans to thorough reviews helps identify potential gaps and areas that may require additional attention. This process ensures that estimates are grounded in a realistic understanding of the testing scope.

---

Importance of Management Support

For testing efforts to be effective, they must be supported by management. This support includes acknowledging the importance of thorough testing, allocating appropriate resources, and respecting the time estimates provided by testing teams. When management understands and values the testing process, it fosters an environment where quality is prioritized.

---

Conclusion

Allocating adequate time for software testing is not a luxury but a necessity. It ensures that the final product meets quality standards and performs reliably for users. By understanding the challenges and implementing strategic estimation practices, organizations can enhance their testing processes, leading to the successful delivery of high-quality software.

---

Recommended Reading

For those interested in delving deeper into software testing and estimation techniques, consider the following books:

• Software Testing: A Craftsman's Approach by Paul C. Jorgensen (affiliate link for purchase)

• Lessons Learned in Software Testing by Cem Kaner, James Bach, and Bret Pettichord (affiliate link for purchase)

• Agile Testing: A Practical Guide for Testers and Agile Teams by Lisa Crispin and Janet Gregory (Purchase - affiliate link)

---

Informative Videos

To further understand the nuances of software testing and time estimation, the following videos provide valuable insights:

Software Testing Tutorial Introduction and Course Topics - Software Testing Bootcamp

5 Types of Testing Software Every Developer Needs to Know!

---

By embracing the importance of allocating sufficient time for testing and implementing effective estimation strategies, software development teams can significantly enhance the quality and reliability of their products.

What is trace-ability alert? How to trigger a trace-ability alert in Test Director?

The process of sending e–mails in order to notify the ones that are responsible whenever some change is made to the project. This can be done by instructing the test director to create an alert whenever a change occurs and send e – mails appropriately. One’s own follow up alerts can also be added. 

There are certain rules called the trace-ability notification rules (based up on the associations that were made in the test director among the tests, requirements and defects) which are activated by the test director administrator for generating the automatic trace-ability alerts.

On what occasions a trace-ability alert issued?

Only for the following issues test director can generate the trace-ability alerts:

1. Whenever a requirement (except change of a status) changes, the designer of the associated tests is notified by the test director.
2. Whenever a requirement having an associated test changes, all the project users are notified by the test director.
3. Whenever the defect status changes to ‘fixed’, the responsible tester of the associated test is notified by the test director.
4. Whenever a test run is successful, the user assigned to the associated test is notified by the test director.

Steps to trigger trace-ability alert

1. Log on to the project  as a different user.
2. Click on the test plan tab to turn on the test plan module which will display the test plan tree. Expand the concerned subject folders and select the required test. A designer box displaying the user name in the details tab in the right pane is seen. One thing to be noted is that whenever an associated requirement changes, the trace-ability notification is only viewed by the designer.
3. Click on the requirements tab to turn on the requirements tree and also make sure that it is in the document view.
4. Among the requirements choose the one that you want to change.
5. For changing the priority of the requirement click on the priority down arrow and select the required priority. This will cause the test director to generate an alert for the test associated with the requirement selected above. Also, an e – mail will be sent to the designer who designed this test.
6. When you are done log out of the project by clicking on the log out button present on the right side of the window.

How to view a trace-ability alert?

This trace-ability change can be viewed for a single entity or all the entities in the project. Here by entity we mean a test, a defect or a test instance. To view the trace-ability alert follow the below mentioned steps:

1. Log on to the project as the designer of the test.
2. Click on the test plan tab to view the test plan tree. Expand the subject folders to display that test. You will see that the test has a trace changes flag which is an indication of the fact that a change was made to the requirement associated with it.
3. Clicking on the trace changes flag for the test will enable you to view the trace-ability alert. Also, the trace changes dialog box will open up. Clicking on the requirement link will make the test director to highlight that particular requirement in the requirements module.
4. For viewing all of the trace-ability alerts click on the trace all changes button in the common test director tool bar. A dialog box listing all the trace-ability changes will open up.
5. Once done close the dialog box. 

What is a follow up alert? How to create follow up alerts in test director?

Test director is mercury interactive’s test management tool. 

- It helps in creating a quality assurance personnel plan and organizing the whole testing process usually termed as the test director testing process.

- It lets you build a data base consisting of the manual as well as automated test cases, test cycles, run tests, reports of the tracking defects and so on. 

- The test director instructs to create alerts automatically and notify the responsible people whenever some changes are encountered by the project. 

- Alerts are generated for the changes that affect the project in one or more than one ways. 

- For generating automatic alerts, the administrator can activate the trace-ability notification rules based on the associations made among the requirements, defects and test.

What is a Follow Up Alert?

- Test director allows to add own follow up flag to a defect, test instance or a specific test so as  to remind oneself to follow up on an issue. 

- When the date of actual follow up arrives, an e – mail is send to the person’s mail box. 

- Test director notifies the tester by adding a trace that changes the flag to the changed entity or by mailing a notification whenever a change is made to the requirement, defect or test in the project. 

- Creating follow-up alerts is always useful since you are always reminded whenever it is required to follow up on some issues. 

Requirements for Follow up Alert

- Test director 8.0 should be installed on your system. 

- You must have access to all the four modules of the test director namely requirements, test plan, test lab and defects. 

- You must have either a sample project or an actual project on which you carry out the exercise.

- Work with a new copy of the project. 

- You should also have either a sample application or an actual application.  

Now we shall discuss the procedure to add a follow up flag to a defect whose status requires to be checked. 

When the follow up date comes, the flag icon is turned to red color and the test director sends a notification via e – mail. One thing that you should always take care of is that the flags have a specific user name which means only the user whose name is on the flag will be able to see it. 

Steps to create a Follow-up Alert

Follow the steps mentioned below to create a follow up alert:

1. Click on the defects tab so as to turn on the defects module.
2. From the defects grid select the defect for which you want to set up a flag to follow  up.
3. Now for creating a follow up alert click on the ‘flag for follow up’ button and a flag for follow up dialog box will open up. Fill in the following details:

a)   Follow up by: select the date.

b)   Description: type:

Once done with filling up the details click ok. A flag icon will be added to the      defect record by the test director.

4. To display the information bar for your follow up alert, double click with the follow up flag on the defect. A defect details dialog box will pop up and will display a yellow information bar with the follow up alert.
5. To close the dialog box click on cancel button.

How to generate graphs for analyzing the testing process in test director?

The graphs that are created during the test director testing process let you keep a track of the progress of the test plan, test runs, defect tracking, requirements and so on. Such graphs can be generated at any point of time during the process and also from any of the test director modules. The graphs created by the test director are based up on the default setting however they can be customized by the user.

A project consists of data of different types. The graphs that you create using the test director can help you a big deal in analyzing the relationships between these different types of data. Each of the modules of the test director comes with a number of graph generating options. After you are done with generating the graph, you can customize its various properties so it comes out exactly as per your specifications and displays the information you want and in the way you want. 

Now we shall mention the steps following which you can generate a defects graph which will show the summary of the defects by status as well as priority levels. 

Steps for generating Defects Graph

Follow the steps:

1. Click on the defects tab to turn on the defects module of the test director. The defects module will be displayed in the defects grid.
2. Now for choosing a graph go to analysis menu, then graphs, then summary, then group by status option. This will open up a defects summary graph. This graph is grouped by status by default.
3. Next you need to clear the default filter. Clicking on the filter button will do the task for you. The filter dialog box will open up. You will see that the detected by field is set to the current user name by default. Here, click the clear button and the applied filter will be removed by the test director.
4. If you want to define a filter for viewing the defects with high to urgent priority then click the filter condition box for the priority field in the filter dialog box. Clicking on the browse button will open up the select filter condition dialog box’. Then select the required logical expression in the right pane and in the left pan select the level. Click OK to save the settings and close this dialog box.
5. Next for defining a filter for viewing the defects that are not closed click the filter condition box for the status field. Again open the select filter condition dialog box by clicking on the browse button. Select the ‘not’ logical expression and select closed in the left pane. Click OK to close this box and once again click OK to close the filter dialog box.
6. For setting the X axis of the graph select priority on the right side of the window for viewing the number of defects according to priority.
7. Clicking on the refresh button will refresh the graph i.e., a new graph will be displayed.
8. For displaying additional defect details click on a bar segment of the graph. A drill down results dialog box will display the defects related to that bar segment. Close this dialog box by clicking on the close button.
9. There are various graph views available such as the data grid view and pie chart. Clicking on the corresponding options will display the graph as a pie chart, grid and so on.
10. Close the graph and click on the back button to go back to the defects module. 

How to call tests with parameters in Test Director?

Testing an application is a complicated process. Test director has provided help in many tasks such as in the organization and management of the different phases of the testing process which is inclusive of various activities such as test planning, requirements analyzation, defects tracking and so on. 

Test director basically provides the tester with a frame work that is well organized for the testing of applications just before their deployment. Test plans typically evolve around the requirements that are new or have been modified therefore; there is a need of having a central data repository for the management and organization of the testing activities. 

Test director proves to be an effective guide while you go through the following tasks:

1. Requirements specification
2. Test planning
3. Test execution
4. Defect tracking etc.

The above mentioned 4 tasks also represent the 4 major phases of the test director testing process. In the phase of test planning you have the following tasks:

1. Defining the testing strategy
2. Defining test subjects
3. Defining tests
4. Creation of the requirements coverage
5. Designing the test steps
6. Automation of the tests
7. Analyzation of the test plan

A test plan tree is constructed and then the tests are executed for locating the defects and assessing the quality. The following tasks are involved:

1. Creation of the test sets
2. Scheduling the runs
3. Running the tests
4. Analyzation of the test results

How to call tests with parameters in test Director?

- When the test steps are designed, you have an option whether or not include a call to a manual test. 

- When the test is executed, this manual test is called as a part of the execution sequence. 

- The test that is called is actually a template test which has the characteristic that it can be reused as a test that is called by other tests. 

- It is possible to pass parameters to a template test. 

- Parameter is a variable for replacing a fixed value. 

- The values of the parameters can be changed by passing the desired value to the test that calls it. 

Example:

- Suppose there is a test in which you need to log-in with a specific user id and password. 

- There might be two users to the same test i.e., administrator and public. 

- For achieving this, two parameters are created to the test namely user id and password. 

- The value of these two parameters then can be modified according to whether log-in has to be public or administrative.

Follow the steps below to call a test with parameters:

1. Firstly, the design steps tab needs to be displayed for the test therefore click on the design steps tab.
2. Select the test with parameters that are required to be called by clicking on the ‘call to test’ button. A ‘select a test’ dialog box will open up.  Type in the name of the test to be found and click find button. Test director will highlight that particular test. Click OK.
3. Again you will get a ‘parameters of test …’ dialog box which will display all the parameters associated with that particular test.
4. Modify the parameter values in the value column according to your requirements. Values to the parameters can be assigned whenever a test is created to call the tests or whenever a test is added to the test set or whenever the test is run.  Click OK. The selected step will be added to the design steps.
5. Re-order the steps
6. Adjust the step size.

How to develop a test plan tree in Test Director?

Testing a software system or application is not a child’s play rather it requires whole lot of focus, organization, management and vigor. Testing phases or tasks such as specification of the testing requirements, planning and execution of the tests, tracking of the defects are made quite easy with the test director. 

In this article we shall discuss about how the test plan trees can be developed using the test director. After the all of the testing requirements have been defined, the testing goals need to be determined by carrying out various activities such as:

1. Examining the testing as well as the system environment.
2. Examining the software system or application under test (SUT and AUT).
3. Examining the testing process

- These three activities are particularly carried out so that the testing strategy designed to achieve the testing goals can be outlined. 

- After testing goals are determined, one proceeds to build a test plan tree. 

- The purpose of this test plan tree is to hierarchically divide the software system or application under testing in to smaller testing units or one can call them ‘subjects’.

- For each subject or unit in the test plan tree some tests are defined consisting of steps. 

- Next, the actions to be performed on the application as well as the expected results are defined for each of those steps. 

- Addition of parameters to the test step adds to its flexibility. 

Now how to keep track of the relationships shared by the testing requirements and tests? 

- Just add links between the two corresponding things.

- Other than being simple, another benefit of adding links is that you can be assured of the compliance with the requirements in all the stages of the testing process. 

- After getting done with this, you decide which all tests you want to get automated. 

- If you see the application as a whole unit to be tested it seems like a very big thing. 

- Here, in the test director, the application is divided into smaller units based up on its functionality with the help of the test plan module. 

- Test plan tree serves all this purpose and is referred to as the graphical representation of the test plan.

- Here the tests are displayed on the basis of the hierarchical relationship in their functions. 

- After all the subjects in the test plan tree have been defined the next step involves creating step for each and adding them to the tree.

- The below mentioned are the steps to be followed:

1. Open and log on the project for which the testing process is going on.
2. Make sure that the test plan module is on display and if it is not click on the test plan module to do so.
3. Now you need to add a subject folder to the test plan tree by clicking on the new folder button. Give a name and description for the folder and hit OK button. You will see a new subject folder under the main subject folder in the test plan tree.
4. Next step is to add a test to the folder we created above by clicking on the new test button. Give a name for test and click OK. You will require to fill in the following details like level, review status and priority. This test then will be added to the test plan tree.
5. Go to the details tab and you can fill up the following details:

a)   Test name

b)   Test designer

c)   Creation date

d)   Test status etc.

e)   description

How to design and copy test cases in test director?

Application testing process is not the one that can be completed in a jiffy. It demands constant input in form of efforts, organization and maintenance. Well, all this becomes easy when you are assisted by mercury interactive’s test management tool.
Test director saves you a great deal of efforts for tasks such as requirements analysis, test planning, test execution, defect tracking etc. here in this article we are going to tell you how you can design as well as copy the test cases in test director. After the tests created for all the subjects have been added to the test plan tree and the basic test information has been defined, the test cases or the test steps are defined.
By defining them we mean that more details or step by step instructions are provided for how that particular test case is to be executed. Each step of a test case consists of two things namely:
1. Actions to be performed on the application under testing or AUT and
2. The expected results.

Test steps can be created either for manual tests or automated tests using test director. For manual testing it is said to be complete when you are done with the designing of the tests.
Then, the test execution can be straightaway be started by using the test plan tree. But in the case of the automated testing, an addition step is to create automated test scripts using any other mercury interactive tool such as Winrunner or some other third party tool.

Steps for designing test cases

Below mentioned are the steps that one can follow for designing a test case:
1. It has to be made sure that the test plan module is on display and if it is not click on the test plan tab to turn it on.
2. The test case for which you are about to design the test steps also needs to be displayed. You can do this by simply clicking on the name of that particular test.
3. Next you need to launch the design step editor by clicking on the ‘design steps lab’.
4. In the design step editor dialog box clicking on the new step button you will get a new step dialog box which will ask you enter a step name which is by default a sequential number.
5. Now for defining that step you require to fill up the following fields and click OK:
         a) Step name
         b) Description
         c) Expected result
6. Last step is to click OK which will close the design step editor and display the design steps.

How to copy the test cases?

In test director you get the option of copying the test cases either from the same project or from some other. Follow the below mentioned steps:
1. You need to turn on the design steps tab and select that particular test case from the test plan tree which you want to be copied.
2. Next step involves selecting the steps of the test cases which you want to be copied. You will observe a gray sidebar, position the mouse pointer there and you will see that the pointer changes to  ->. Now hold down the shift and select the steps you want to be copied.
3. By using the copy steps copy down all the selected steps.
4. Next paste the steps where you want them to be copied in the test plan tree by using the paste steps button in the design steps tab.

How do you modify and convert requirements in Test Director?

There is no doubt in the fact that one kicks off a testing process by inputting the specification of the requirements employing the requirements module of the test director. Requirements are a necessity in the testing process. Also, the foundation on which a testing team carries out the testing process is laid down by the requirements itself. The definition of the requirements is represented in the form of what is called a requirements tree. This is actually a graphical representation of the requirements as stated in the document view with the only difference being of hierarchical display. 

The requirements can be grouped as well as sorted out in a requirements tree. The following tasks can also be carried out:

1. Task allocation monitoring.
2. Monitoring the progress of the requirements.
3. Generation of the detailed graphs and reports.

Once the tests have been created in the test plan module they have to be linked to the corresponding requirements. 

Here in this article, we talk about the modification and conversion of the requirements in the test director. 

One can modify the requirements by following the below mentioned step sequence:

1. First, make sure that the requirements module is available on display. If in case it is not you need to open it using the requirements tab. Both the requirements tree as well as the document view will be displayed.
2. Your next step is to copy that particular requirement to which you want to make modifications from the requirements tree by clicking on the copy option. Next clicking on the paste option and you will get a warning saying that you are duplicating the requirement. Click OK and the requirement will be pasted in the same hierarchy level as that of the original requirement. Suffix _copy_ is added to the name of the requirement.
3. Next step, is to rename the requirement by following the usual procedure for renaming an object.
4. Next, move this requirement to a different location but in the same requirements tree. But the requirements should be pasted as child requirement. Click OK for confirmation and drag the requirement to any location you want in the requirements tree.
5. For deleting this requirement as well its child requirement use the delete option.

Once all the requirements have been created and defined, they can be used as a basis for providing definition of the test plan tree module. The conversion to test wizards can be used to get assistance for designing the test plan tree. Using this wizard you can convert the selected requirements from the requirement tree in to subjects or tests for the test plan tree.

Steps for conversion of Requirements

Now the below mentioned steps can be followed for the conversion of the requirements:

1. For the modification procedure make sure that the requirements is up for display and if it is not there do so by clicking on the requirements tab.
2. From the various requirements in the requirements tree select the one which you want to be converted.
3. Now launch the convert to tests wizard from the tool menu and from that click on ‘convert selected’ option.
4. You can go for the automatic conversion method by taking second option i.e., ‘convert lowest child requirements to tests’ for the conversion of the selected requirements in to tests.
5. Now clicking on the next button will start the conversion process and after the conversion the results will be displayed in the step 2 dialog box. 

How do you define and view requirements in Test Director?

Test director is currently available as a plug in or add – on as a support for HP quality center and works like a test management tool. The earlier versions of the test director i.e., version 6 and below worked as stand-alone desk top applications.

However, the next version i.e., the test director 7 was a standalone web application and was known to work on any of the browsers that happened to be supporting active technology. For all the testers world wide it has been easy to integrate with the other mercury interactive tools via test director.

Three facts regarding test director:

1. This tool is not going to work out for the collection of the requirements of a software system or application.
2. It is not an automated testing tool.
3. It cannot be integrated with the products save mercury interactive products.

Test director comes with four specific modules namely:

1. Requirements module
2. Test plan module
3. Test lab module and
4. Defects module

How can we define and view requirements in the test director?

- This is done using the requirements module. 

- In every test management process, specification of the requirements is the first important step. 

- It involves analyzation of the software system or application under test and determination of the requirements of testing that application.

- Requirements analysis somewhat helps in carrying out the coverage analysis. - The following tasks are involved:

1. Addition of new requirements or editing of the previously added ones.
2. Addition and editing of the child requirements.
3. Linking of the requirements to the associated defects.
4. Analyzation of the coverage.

- The requirements analyzation phase follows through the below mentioned steps:

1. Defining the scope: The scope of the requirements includes test goals and objectives and can be determined using the requirements documentation.
2. Creation of the requirements: A requirements tree needs to be built so that all of the testing requirements can be defined.
3. Providing details for the requirements: Detailing involves adding attachments, assigning priority levels to all the requirements if required for testing.
4. Analyzation of the requirements: This phase involves generation of the reports consisting of the graphs to provide an assistance in the analyzation of the testing requirements.

Steps for Defining Requirements

Follow the below mentioned steps for defining the requirements:

1. Launch the test director demo project. You will require to log on to the project if in case the project is not open.
2. Now clicking on the requirements tab will display the requirements module or the requirements tree.
3. One thing that you need to be sure of is that the document view of the requirements is also displayed.
4. Click on the new requirement option which will open the new requirement dialog box. Fill in the details and hit OK.
5. Click new child requirement button for adding a requirement as a lower level of hierarchy.

Steps for Viewing Requirements

For viewing the requirements follow the below mentioned steps:

1. First step is making sure that the requirements module is displayed and if not click on the requirements and turn on the document view of the requirements tree.
2. You can zoom in as well as zoom out of the requirements tree using the zoom in and zoom out buttons.
3. In some cases you may require to view the numeration of requirements. 
4. To view numerations go to view menu and click on the numeration option. If you make any changes in the requirements the same is updated by the test director and numerations are renumbered. 

What is a Silk Test Test plan? What are the types of text lines in a test plan file?

A silk test plan consists of large amounts of data as well as information based on which are the details of the plan which in turn will be used in the organization and the development of the software system or application. 

It has three basic qualities as mentioned below:

1. Well structured
2. Hierarchical
3. Ideal model

A silk test test plan constitutes of two parts which are entirely different:

1. First part consists of an outline which gives a detailed description of the all the requirements of the testing process.
2. Second part consists of a statement which establishes a relationship between the outline of the first part and 4test scripts as well as test cases which are bound to implement the requirements defined above.

What is a Silk Test Plan?

- Test plan helps in achieving a guided way for the creation as well as execution of the test cases. 

- A new test plan can be created by following the below mentioned steps:

1. Go to the file menu and then click on new option.
2. From the drop down list that follows select test plan and hit OK. You will get a test plan window. Fill in the required fields and click OK.

- This is a known fact that silk test specializes in the field of functionality as well as regression testing and has been a known product when it comes to web, java or windows based applications. 

- Silk test provides you with two ways for defining or creating the automated tests:

1. By using the record test case command for recording the actions and the verification of steps.
2. Using visual 4test scripting language by writing the test cases manually.

- Test plans in silk test are stored as ‘test plan (.pln)’ file type. 

- This file type is sometimes used for making combinations of the test scripts. 

- The basic purpose of a silk test test plan is to provide a frame work for the testing process and also for the organization and maintenance of the testing requirements. 

Benefits of using a Test Plan

Using a test plan has following benefits:

1. With test plan you have a chance to implement top down approach for defining the testing requirements, developing thoughts and refining the requirements.
2. Attributes can be assigned to individual tests or group of tests.
3. Redundancy is reduced single only actually implementing statements are allowed.
4. Can be used as a comprehensive inventory of requirements consisting of most general as well as specific requirements.

What kind of text lines are there in a test plan file?

Test plan file consists of 5 types of text lines that we have described below:

1. First type of text lines are the comments which are usually marked in green color.These types of text lines provide commentary type of information regarding the test code.
2. Group Description: This type of text lines are represented in bold black color. Furthermore, they are included so as to provide a description of a group of tests rather than describing individual tests. Usually, a test plan consists of many tests which are then grouped in to multiple levels of various groups.
3. Test Description: This type of text lines are written in blue color and are meant for showcasing the description of the individual tests only.
4. Test plan statement: This type of text lines in a test plan file provide information regarding the relations to the following elements:

a)   Test cases

b)   Link scripts

c)   Test data

d)   Closed sub test plans

e)   Include files to a test plan.

These are marked in red color.

5. Open sub plan file marker: These text lines are marked in magenta color and thus providing info regarding relations to link sub test plans with the master plan.

What are the challenges of testing Web Applications? How to use Silk Test with Web Applications?

Web applications are a rage these days and thus a fast delivery of web applications is in urgent need. But at the same time it is important to keep the security of these web applications in check. 

However, web testers continue to face some challenges while testing the web applications and this is what that we are going to discuss in this article. 

What are Web Applications?

- As we are familiar with the growing popularity of the web applications, with the time, new and advance features are being introduced in the web applications.

- It makes them one of the most popular means for the development of the commercial systems. 

- Nowadays, almost all the companies opt for developing web based software wherever and for whatever possible. 

- This is so because with the help of web applications the company can easily cater to the needs of a large number of people. 

- Also, once the infrastructure of the application is put in place the deployment of the apps becomes quite easy. 

- The web applications are powerful assets and using them, a feature rich content can be provided to a large audience across the globe at quite an economical cost.

- Hence, it becomes more and more daunting to test these complex applications. 

- For the web applications the two factors continue to be the most important:

1. Accessibility and
2. Security

Challenges in testing Web Application

While on one side, the company wants to cater to the users all over the world, on the other side their web application can fall prey to some grave security issues. Thus, only web application testing stands a chance to secure the data as well the organization. 

- The design and nature of every web application is somewhat unique to it and so it is possible for the users to follow different paths of usage.

- In such cases, it is necessary to ensure that all paths are working well by testing all the permutations and combinations. 

- Also, all the software applications are not self explanatory. 

- Users of a web application are from various back grounds and those who are from a non technical background may find it hard to use the application. 

- This does affects the design of the application and therefore should be tested during the usability testing of the application. 

- For intranet based web applications, it is possible for the developers to make assumptions regarding the audience but this is impossible for the internet based web applications. 

- Today, there are many web browsers available and so different browsers are used by different users. 

- Thus, there is a need to test this aspect since it can be ensured that the web application is compatible with all the platforms.

How is web testing done in SilkTest?

- Web testing is possible using the Borland’s silk test. 

- Till now, it has been proven to be the leading functional testing tool in the software industry when it comes to testing e- business applications either based up on windows, web, java or client or server based and so on. 

- Silk test is used for the following purposes:

1. Test planning
2. Test management
3. Direct data base access and validation

- It also comes with a built – in recovery system for the purpose of unattended testing of the web applications across multiple browsers, platforms and technologies.