The Experts below are selected from a list of 165 Experts worldwide ranked by ideXlab platform

Sathish Kumar - One of the best experts on this subject based on the ideXlab platform.

  • Efficient and change-resilient test automation: An industrial case study
    Proceedings - International Conference on Software Engineering, 2013
    Co-Authors: Suresh Thummalapenta, Sivagami Gnanasundaram, Deepa D. Nagaraj, Pranavadatta Devaki, Sampath Kumar, Saurabh Sinha, Satish Chandra, Sathish Kumar
    Abstract:

    Test automation, which involves the conversion of manual test\ncases to executable test scripts, is necessary to carry out efficient\nregression testing of GUI-based Applications. However, test automation\ntakes significant investment of time and skilled effort. Moreover, it is\nnot a one-time investment: as the Application or its environment\nevolves, test scripts demand continuous patching. Thus, it is\nchallenging to perform test automation in a cost-effective manner. At\nIBM, we developed a tool, called ATA [1], [2], to meet this challenge.\nATA has novel features that are designed to lower the cost of initial\ntest automation significantly. Moreover, ATA has the ability to patch\nscripts automatically for certain types of Application or environment\nchanges. How well does ATA meet its objectives in the real world? In\nthis paper, we present a detailed case study in the context of a\nchallenging production environment: an Enterprise Web Application that\nhas over 6500 manual test cases, comes in two variants, evolves\nfrequently, and needs to be tested on multiple browsers in\ntime-constrained and resource-constrained regression cycles. We measured\nhow well ATA improved the efficiency in initial automation. We also\nevaluated the effectiveness of ATA's change-resilience along multiple\ndimensions: Application versions, browsers, and browser versions. Our\nstudy highlights several lessons for test-automation practitioners as\nwell as open research problems in test automation.

  • ICSE - Efficient and change-resilient test automation: an industrial case study
    2013 35th International Conference on Software Engineering (ICSE), 2013
    Co-Authors: Suresh Thummalapenta, Sivagami Gnanasundaram, Deepa D. Nagaraj, Pranavadatta Devaki, Sampath Kumar, Saurabh Sinha, Satish Chandra, Sathish Kumar
    Abstract:

    Test automation, which involves the conversion of manual test cases to executable test scripts, is necessary to carry out efficient regression testing of GUI-based Applications. However, test automation takes significant investment of time and skilled effort. Moreover, it is not a one-time investment: as the Application or its environment evolves, test scripts demand continuous patching. Thus, it is challenging to perform test automation in a cost-effective manner. At IBM, we developed a tool, called ATA [1], [2], to meet this challenge. ATA has novel features that are designed to lower the cost of initial test automation significantly. Moreover, ATA has the ability to patch scripts automatically for certain types of Application or environment changes. How well does ATA meet its objectives in the real world? In this paper, we present a detailed case study in the context of a challenging production environment: an Enterprise Web Application that has over 6500 manual test cases, comes in two variants, evolves frequently, and needs to be tested on multiple browsers in time-constrained and resource-constrained regression cycles. We measured how well ATA improved the efficiency in initial automation. We also evaluated the effectiveness of ATA's change-resilience along multiple dimensions: Application versions, browsers, and browser versions. Our study highlights several lessons for test-automation practitioners as well as open research problems in test automation.

Suresh Thummalapenta - One of the best experts on this subject based on the ideXlab platform.

  • ISSTA - Efficient and flexible GUI test execution via test merging
    Proceedings of the 2013 International Symposium on Software Testing and Analysis, 2013
    Co-Authors: Pranavadatta Devaki, Suresh Thummalapenta, Nimit Singhania, Saurabh Sinha
    Abstract:

    As a test suite evolves, it can accumulate redundant tests. To address this problem, many test-suite reduction techniques, based on different measures of redundancy, have been developed. A more subtle problem, that can also cause test-suite bloat and that has not been addressed by existing research, is the accumulation of similar tests. Similar tests are not redundant by any measure; but, they contain many common actions that are executed repeatedly, which over a large test suite, can degrade execution time substantially. We present a test merging technique for GUI tests. Given a test suite, the technique identifies the tests that can be merged and creates a merged test, which covers all the Application states that are exercised individually by the tests, but with the redundant common steps executed only once. The key novelty in the merging technique is that it compares the dynamic states induced by the tests to identify a semantically meaningful interleaving of steps from different tests. The technique not only improves the efficiency of test execution, but also ensures that there is no loss in the fault-revealing power of the original tests. In the empirical studies, conducted using four open-source Web Applications and one proprietary Enterprise Web Application, in which over $3300$ test cases and 19600 test steps were analyzed, the technique reduced the number of test steps by 29% and the test-execution time by 39%.

  • Efficient and change-resilient test automation: An industrial case study
    Proceedings - International Conference on Software Engineering, 2013
    Co-Authors: Suresh Thummalapenta, Sivagami Gnanasundaram, Deepa D. Nagaraj, Pranavadatta Devaki, Sampath Kumar, Saurabh Sinha, Satish Chandra, Sathish Kumar
    Abstract:

    Test automation, which involves the conversion of manual test\ncases to executable test scripts, is necessary to carry out efficient\nregression testing of GUI-based Applications. However, test automation\ntakes significant investment of time and skilled effort. Moreover, it is\nnot a one-time investment: as the Application or its environment\nevolves, test scripts demand continuous patching. Thus, it is\nchallenging to perform test automation in a cost-effective manner. At\nIBM, we developed a tool, called ATA [1], [2], to meet this challenge.\nATA has novel features that are designed to lower the cost of initial\ntest automation significantly. Moreover, ATA has the ability to patch\nscripts automatically for certain types of Application or environment\nchanges. How well does ATA meet its objectives in the real world? In\nthis paper, we present a detailed case study in the context of a\nchallenging production environment: an Enterprise Web Application that\nhas over 6500 manual test cases, comes in two variants, evolves\nfrequently, and needs to be tested on multiple browsers in\ntime-constrained and resource-constrained regression cycles. We measured\nhow well ATA improved the efficiency in initial automation. We also\nevaluated the effectiveness of ATA's change-resilience along multiple\ndimensions: Application versions, browsers, and browser versions. Our\nstudy highlights several lessons for test-automation practitioners as\nwell as open research problems in test automation.

  • ICSE - Efficient and change-resilient test automation: an industrial case study
    2013 35th International Conference on Software Engineering (ICSE), 2013
    Co-Authors: Suresh Thummalapenta, Sivagami Gnanasundaram, Deepa D. Nagaraj, Pranavadatta Devaki, Sampath Kumar, Saurabh Sinha, Satish Chandra, Sathish Kumar
    Abstract:

    Test automation, which involves the conversion of manual test cases to executable test scripts, is necessary to carry out efficient regression testing of GUI-based Applications. However, test automation takes significant investment of time and skilled effort. Moreover, it is not a one-time investment: as the Application or its environment evolves, test scripts demand continuous patching. Thus, it is challenging to perform test automation in a cost-effective manner. At IBM, we developed a tool, called ATA [1], [2], to meet this challenge. ATA has novel features that are designed to lower the cost of initial test automation significantly. Moreover, ATA has the ability to patch scripts automatically for certain types of Application or environment changes. How well does ATA meet its objectives in the real world? In this paper, we present a detailed case study in the context of a challenging production environment: an Enterprise Web Application that has over 6500 manual test cases, comes in two variants, evolves frequently, and needs to be tested on multiple browsers in time-constrained and resource-constrained regression cycles. We measured how well ATA improved the efficiency in initial automation. We also evaluated the effectiveness of ATA's change-resilience along multiple dimensions: Application versions, browsers, and browser versions. Our study highlights several lessons for test-automation practitioners as well as open research problems in test automation.

Bradley Wehrwein - One of the best experts on this subject based on the ideXlab platform.

  • relating requirements to a user interface architecture for a rich Enterprise Web Application
    TEAA'06 Proceedings of the 2nd international conference on Trends in enterprise application architecture, 2006
    Co-Authors: Rajanikanth Tanikella, Gilberto Matos, Grace Tai, Bradley Wehrwein
    Abstract:

    Over the past few years, the demand for richer user interfaces and fast performance for Web Applications has also had its effect on Enterprise Web UI development. Solutions such as rich thin client frameworks and rich internet Application (RIA) frameworks have emerged, alongside technologies like AJAX and Adobe Flex. At Siemens Corporate Research, our recent experience in developing a scalable Enterprise Web Application with an agile methodology, however, has indicated that implementation decisions are often made without fully understanding the implications that the desired UI concept and look and feel have on the implementation. This paper presents a conceptual UI architecture and, for each aspect of the architecture, examines the types of requirements that should be gleaned from the various UI requirements documents. We make recommendations to help bridge the gap between user interface design specifications and user interface architectural specifications, including impacts on implementation-level architecture.

  • TEAA - Relating requirements to a user interface architecture for a rich Enterprise Web Application
    Lecture Notes in Computer Science, 1
    Co-Authors: Rajanikanth Tanikella, Gilberto Matos, Grace Tai, Bradley Wehrwein
    Abstract:

    Over the past few years, the demand for richer user interfaces and fast performance for Web Applications has also had its effect on Enterprise Web UI development. Solutions such as rich thin client frameworks and rich internet Application (RIA) frameworks have emerged, alongside technologies like AJAX and Adobe Flex. At Siemens Corporate Research, our recent experience in developing a scalable Enterprise Web Application with an agile methodology, however, has indicated that implementation decisions are often made without fully understanding the implications that the desired UI concept and look and feel have on the implementation. This paper presents a conceptual UI architecture and, for each aspect of the architecture, examines the types of requirements that should be gleaned from the various UI requirements documents. We make recommendations to help bridge the gap between user interface design specifications and user interface architectural specifications, including impacts on implementation-level architecture.

Saurabh Sinha - One of the best experts on this subject based on the ideXlab platform.

  • ISSTA - Efficient and flexible GUI test execution via test merging
    Proceedings of the 2013 International Symposium on Software Testing and Analysis, 2013
    Co-Authors: Pranavadatta Devaki, Suresh Thummalapenta, Nimit Singhania, Saurabh Sinha
    Abstract:

    As a test suite evolves, it can accumulate redundant tests. To address this problem, many test-suite reduction techniques, based on different measures of redundancy, have been developed. A more subtle problem, that can also cause test-suite bloat and that has not been addressed by existing research, is the accumulation of similar tests. Similar tests are not redundant by any measure; but, they contain many common actions that are executed repeatedly, which over a large test suite, can degrade execution time substantially. We present a test merging technique for GUI tests. Given a test suite, the technique identifies the tests that can be merged and creates a merged test, which covers all the Application states that are exercised individually by the tests, but with the redundant common steps executed only once. The key novelty in the merging technique is that it compares the dynamic states induced by the tests to identify a semantically meaningful interleaving of steps from different tests. The technique not only improves the efficiency of test execution, but also ensures that there is no loss in the fault-revealing power of the original tests. In the empirical studies, conducted using four open-source Web Applications and one proprietary Enterprise Web Application, in which over $3300$ test cases and 19600 test steps were analyzed, the technique reduced the number of test steps by 29% and the test-execution time by 39%.

  • Efficient and change-resilient test automation: An industrial case study
    Proceedings - International Conference on Software Engineering, 2013
    Co-Authors: Suresh Thummalapenta, Sivagami Gnanasundaram, Deepa D. Nagaraj, Pranavadatta Devaki, Sampath Kumar, Saurabh Sinha, Satish Chandra, Sathish Kumar
    Abstract:

    Test automation, which involves the conversion of manual test\ncases to executable test scripts, is necessary to carry out efficient\nregression testing of GUI-based Applications. However, test automation\ntakes significant investment of time and skilled effort. Moreover, it is\nnot a one-time investment: as the Application or its environment\nevolves, test scripts demand continuous patching. Thus, it is\nchallenging to perform test automation in a cost-effective manner. At\nIBM, we developed a tool, called ATA [1], [2], to meet this challenge.\nATA has novel features that are designed to lower the cost of initial\ntest automation significantly. Moreover, ATA has the ability to patch\nscripts automatically for certain types of Application or environment\nchanges. How well does ATA meet its objectives in the real world? In\nthis paper, we present a detailed case study in the context of a\nchallenging production environment: an Enterprise Web Application that\nhas over 6500 manual test cases, comes in two variants, evolves\nfrequently, and needs to be tested on multiple browsers in\ntime-constrained and resource-constrained regression cycles. We measured\nhow well ATA improved the efficiency in initial automation. We also\nevaluated the effectiveness of ATA's change-resilience along multiple\ndimensions: Application versions, browsers, and browser versions. Our\nstudy highlights several lessons for test-automation practitioners as\nwell as open research problems in test automation.

  • ICSE - Efficient and change-resilient test automation: an industrial case study
    2013 35th International Conference on Software Engineering (ICSE), 2013
    Co-Authors: Suresh Thummalapenta, Sivagami Gnanasundaram, Deepa D. Nagaraj, Pranavadatta Devaki, Sampath Kumar, Saurabh Sinha, Satish Chandra, Sathish Kumar
    Abstract:

    Test automation, which involves the conversion of manual test cases to executable test scripts, is necessary to carry out efficient regression testing of GUI-based Applications. However, test automation takes significant investment of time and skilled effort. Moreover, it is not a one-time investment: as the Application or its environment evolves, test scripts demand continuous patching. Thus, it is challenging to perform test automation in a cost-effective manner. At IBM, we developed a tool, called ATA [1], [2], to meet this challenge. ATA has novel features that are designed to lower the cost of initial test automation significantly. Moreover, ATA has the ability to patch scripts automatically for certain types of Application or environment changes. How well does ATA meet its objectives in the real world? In this paper, we present a detailed case study in the context of a challenging production environment: an Enterprise Web Application that has over 6500 manual test cases, comes in two variants, evolves frequently, and needs to be tested on multiple browsers in time-constrained and resource-constrained regression cycles. We measured how well ATA improved the efficiency in initial automation. We also evaluated the effectiveness of ATA's change-resilience along multiple dimensions: Application versions, browsers, and browser versions. Our study highlights several lessons for test-automation practitioners as well as open research problems in test automation.

Pranavadatta Devaki - One of the best experts on this subject based on the ideXlab platform.

  • ISSTA - Efficient and flexible GUI test execution via test merging
    Proceedings of the 2013 International Symposium on Software Testing and Analysis, 2013
    Co-Authors: Pranavadatta Devaki, Suresh Thummalapenta, Nimit Singhania, Saurabh Sinha
    Abstract:

    As a test suite evolves, it can accumulate redundant tests. To address this problem, many test-suite reduction techniques, based on different measures of redundancy, have been developed. A more subtle problem, that can also cause test-suite bloat and that has not been addressed by existing research, is the accumulation of similar tests. Similar tests are not redundant by any measure; but, they contain many common actions that are executed repeatedly, which over a large test suite, can degrade execution time substantially. We present a test merging technique for GUI tests. Given a test suite, the technique identifies the tests that can be merged and creates a merged test, which covers all the Application states that are exercised individually by the tests, but with the redundant common steps executed only once. The key novelty in the merging technique is that it compares the dynamic states induced by the tests to identify a semantically meaningful interleaving of steps from different tests. The technique not only improves the efficiency of test execution, but also ensures that there is no loss in the fault-revealing power of the original tests. In the empirical studies, conducted using four open-source Web Applications and one proprietary Enterprise Web Application, in which over $3300$ test cases and 19600 test steps were analyzed, the technique reduced the number of test steps by 29% and the test-execution time by 39%.

  • Efficient and change-resilient test automation: An industrial case study
    Proceedings - International Conference on Software Engineering, 2013
    Co-Authors: Suresh Thummalapenta, Sivagami Gnanasundaram, Deepa D. Nagaraj, Pranavadatta Devaki, Sampath Kumar, Saurabh Sinha, Satish Chandra, Sathish Kumar
    Abstract:

    Test automation, which involves the conversion of manual test\ncases to executable test scripts, is necessary to carry out efficient\nregression testing of GUI-based Applications. However, test automation\ntakes significant investment of time and skilled effort. Moreover, it is\nnot a one-time investment: as the Application or its environment\nevolves, test scripts demand continuous patching. Thus, it is\nchallenging to perform test automation in a cost-effective manner. At\nIBM, we developed a tool, called ATA [1], [2], to meet this challenge.\nATA has novel features that are designed to lower the cost of initial\ntest automation significantly. Moreover, ATA has the ability to patch\nscripts automatically for certain types of Application or environment\nchanges. How well does ATA meet its objectives in the real world? In\nthis paper, we present a detailed case study in the context of a\nchallenging production environment: an Enterprise Web Application that\nhas over 6500 manual test cases, comes in two variants, evolves\nfrequently, and needs to be tested on multiple browsers in\ntime-constrained and resource-constrained regression cycles. We measured\nhow well ATA improved the efficiency in initial automation. We also\nevaluated the effectiveness of ATA's change-resilience along multiple\ndimensions: Application versions, browsers, and browser versions. Our\nstudy highlights several lessons for test-automation practitioners as\nwell as open research problems in test automation.

  • ICSE - Efficient and change-resilient test automation: an industrial case study
    2013 35th International Conference on Software Engineering (ICSE), 2013
    Co-Authors: Suresh Thummalapenta, Sivagami Gnanasundaram, Deepa D. Nagaraj, Pranavadatta Devaki, Sampath Kumar, Saurabh Sinha, Satish Chandra, Sathish Kumar
    Abstract:

    Test automation, which involves the conversion of manual test cases to executable test scripts, is necessary to carry out efficient regression testing of GUI-based Applications. However, test automation takes significant investment of time and skilled effort. Moreover, it is not a one-time investment: as the Application or its environment evolves, test scripts demand continuous patching. Thus, it is challenging to perform test automation in a cost-effective manner. At IBM, we developed a tool, called ATA [1], [2], to meet this challenge. ATA has novel features that are designed to lower the cost of initial test automation significantly. Moreover, ATA has the ability to patch scripts automatically for certain types of Application or environment changes. How well does ATA meet its objectives in the real world? In this paper, we present a detailed case study in the context of a challenging production environment: an Enterprise Web Application that has over 6500 manual test cases, comes in two variants, evolves frequently, and needs to be tested on multiple browsers in time-constrained and resource-constrained regression cycles. We measured how well ATA improved the efficiency in initial automation. We also evaluated the effectiveness of ATA's change-resilience along multiple dimensions: Application versions, browsers, and browser versions. Our study highlights several lessons for test-automation practitioners as well as open research problems in test automation.