ABSTRACT

In software engineering, performance testing is testing that is performed, to determine how fast some aspect of a system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage. Performance testing is a subset of Performance engineering, an emerging computer science practice which strives to build performance into the design and architecture of a system, prior to the onset of actual coding effort

In recent years, Web applications have grown so quickly that they have already become crucial to the success of businesses. However, since they are built on Internet and open standard technologies, Web applications bring new challenges to researchers, such as dynamic behaviors, heterogeneous representations, novel control flow and data flow mechanisms, etc. In this paper, we propose an agent-based approach for Web application testing. While the agent-based framework greatly reduces the complexity of Web applications, a four-level dataflow test approach can be employed to perform structure testing on them. In this approach, data flow analysis is performed as function level testing, function cluster level testing, object level testing, and Web application level testing, from low abstract level to high abstract level. Each test agent in the framework takes charge of the testing in an abstract level for a particular type of Web document or object.

ORGANIZATION OF WORK

This project work is primarily designed to give an insight to Web test tool application design and measure performance

Chapter one talks about introduction to Web test tool application design and measure performance, study of problem and objectives as well as definition of the scope

Chapter two comprises the literature review Chapter three gives the detailed information about the existing (old) system, while chapter four and five deals with the design and implantation of new system

Chapter six documents the project work, while chapter seven summaries, conclusion and suggestions were made

                    

                     TABLE OF CONTENT

TITLE PAGE                                                              

CERTIFICATION                                                 

APPROVAL                                                        

DEDICATION                                                             

ACKNOWLEDGEMENT                                         

ABSTRACT                                                        

ORGANIZATION OF WORK                                          

TABLE OF CONTENT                                                   

CHAPTER ONE

10    INTRODUCTION                                        

11    STATEMENT OF PROBLEM                                  

12    AIMS AND OBJECTIVES                                      

13    PURPOSE OF STUDY                                          

14    SIGNIFICANT OF STUDY                                     

15    SCOPE/DELIMITATIONS                                     

16    LIMITATIONS/CONSTRAINTS                              

17    ASSUMPTION OF STUDY                                    

18    DEFINITION OF TERMS                                      

CHAPTER TWO

20    LITERATURE REVIEW                                         

CHAPTER THREE

30    DESCRIPTION AND ANALYSIS OF THE EXISTING SYSTEM      

31    FACT-FINDING METHOD/ METHODOLOGY            

32    ORGANIZATIONAL STRUCTURE/ORGANOGRAM     

33    OBJECTIVES OF THE EXISTING SYSTEM              

34    INPUT, PROCESS, AND OUTPUT ANALYSIS   

341 INPUT ANALYSIS                                               

342 PROCESS ANALYSIS                                   

343 OUTPUT ANALYSIS                                            

35    INFORMATION FLOW DIAGRAM                          

36    PROBLEMS OF THE EXISTING SYSTEM                

37    JUSTIFICATION OF THE NEW SYSTEM         

CHAPTER FOUR

40    DESIGN OF THE NEW SYSTEM                            

41    DESIGN STANDARD                                           

42    OUTPUT SPECIFICATION AND DESIGN                 

43    INPUT SPECIFICATION AND DESIGN                   

431 FILE DESIGN                                                     

44    PROCEDURE CHART                                           

45    SYSTEMS FLOWCHART                                               

46    SYSTEM REQUIREMENTS                                   

461 HARDWARE REQUIREMENTS                                      

462 SOFTWARE REQUIREMENTS                                       

463 OPERATIONAL REQUIREMENTS                           

464 PERSONNEL REQUIREMENTS                              

CHAPTER FIVE

50    IMPLEMENTATION                                             

5

1    DESIGN STANDARD                                           

52    PROGRAM DESIGN                                            

521 PROGRAM FLOWCHART                                      

522 PSEUDO CODE                                                  

53    CODING                                                           

54    TEST DATA/TEST RUN                                       

55    USER TRAINING AN OVERVIEW                        

56    CUTOVER PROCESS                                           

CHAPTER SIX

60    DOCUMENTATION                             

61    THE USER DOCUMENTATION                              

62    THE PROGRAMMER DOCUMENTATION                 

CHAPTER SEVEN 70    RECOMMENDATIONS, SUMMARY AND CONCLUSION

71    RECOMMENDATION                                           

72    SUMMARY                                                         

73    CONCLUSION                                                    

REFERENCES                                                            

BIBLIOGRAPHY

APPENDIX                                                                

SOURCE LISTING                                                       

LIST OF FIGURES                                                      

CHAPTER ONE

10    INTRODUCTION

In recent years, Web applications (WAs) have grown so quickly that they have already become crucial to the success of businesses However, since they are built on Internet and open standard technologies, WAs possess their own unique features, such as dynamic behaviors, heterogeneous representations, and novel data handling mechanisms These features provide concrete support to the success of WAs, but they bring new challenges to researchers and developers, especially in regard to testing WAs and ensuring their quality Testing approaches for non-WAs have to be extended to handle these features before they are used in WA testing This paper presents an agent-based approach to perform data-flow testing of WAs More precisely, the data-flow testing will be performed by autonomous test agents at the method level, object level, and object cluster level, from low abstraction level to high abstraction level In the process of the recommended data-flow testing, an agent-based WA testing system (WAT) will automatically generate and coordinate test agents to decompose the task of testing an entire WA into a set of subtasks that can be accomplished by test agents The test agents, rooted in the Belief-Desire-Intention (BDI) model, cooperate with each other to complete the testing of a WA An example is used to show the feasibility of the proposed approach

11    BACKGROUND OF STUDY

Kia Motors is South Korea’s second largest automobile manufacturer, having sold over 16 million cars in 2009[2]

The word Kia derives from Korean words meaning “to arise to the world from Asia”

South Korea’s oldest car company, Kia was founded on June 9, 1944 as a manufacturer of steel tubing and bicycle parts by hand “ and has operated as one of the country’s Chaebols since In 1952, Kia changed its name from Kyungsung Precision Industry,[9] and later built motorcycles (starting in 1957), trucks (1962) and cars (1974) The company opened its first integrated automotive assembly plant in 1973, the Sohari Plant Starting in 1986, in partnership with Ford, Kia produced several Mazda derived vehicles for both domestic sales in South Korea into other countries These models include the Pride (based on the Mazda 121) and Avella, which were sold in North Americand Australasiaas the Ford Festiva and Ford Aspire

In 1992, Kia Motors America was incorporated in the United States The first Kia-branded vehicles in the United States were sold from four dealerships in Portland, Oregon in February 1994 Since then, Kia expanded methodically one region at a time Dealers in 1994 sold the Sephia, and a few years later the United States line expanded with the addition of the Sportage

However, Kia’s bankruptcy in 1997, part of the Asian financial crisis, resulted in 51% of the company being acquired in 1998 by South Korean rival Hyundai Motor Company, outbidding Ford Motor Company which had owned an interest in Kia Motors since 1986[10] Subsequently, however, Hyundai has divested some of its ownership of Kia Motors,[11] and currently Hyundai Motor Company owns less than 40% of the company

In October 2006, Kia Motors America broke ground for Kia Motors Manufacturing Georgia in West Point, Georgia, representing a $1 billion USD investment for the company[12] Kia Motors Manufacturing Georgia opened in February, 2010 For 2009, KMA recorded its 15th consecutive year of increased US market share

12    STATEMENT OF PROBLEM

Owing to: