Software testing is an important part of any software development. With the emphasis on developing systems using modern object oriented technologies, a critically-sensitive issue arises in the area of testing. While traditional testing is reasonably well understood, object oriented testing presents a host of new challenges. This paper focuses on what differentiates the two in test cases, testing levels, and OO features affecting testing.

/pdf/a-comparison-of-software-testing-using-the-object-oriented-56qbhtqh1d.pdf

A Comparison of Software Testing Using the Object-Oriented Paradigm and Traditional Testing

Software measurement is widely recognized as an essential part of understanding, controlling, monitoring, predicting, and evaluating software development and maintenance projects. Both, software process improvement (SPI) and software measurement literature include many case studies of successful companies and descriptions of their measurement programs. However, there are still concerns on how to design efficient strategic measurement programs. These concerns include the lack of involvement of the SEO’s personnel, bad alignment with its strategy and improvement initiative, difficulty to justify the utility of using standards or improvement initiatives, etc. All of the former results in inadequate measurement programs that often lead to poor decisions and economic loss. This paper describes a pilot study to observe and analyze the operation of measurement teams when using measurement methods such as Balanced Objective-Quantifiers Method (BOQM), Practical Software Measurement (PSM) and Balanced Scorecard and Goal-Driven Measurement (BSC&GQ[I]M) to design a strategic measurement program. From the results of the study, we gained some insight on common difficulties and problems, which are useful to consider when designing of strategic measurement programs. This paper describes an important milestone in achieving our main research goal, evaluate and find suggestions to design a strategic measurement program aligned correctly with the strategic goals, for effective decision making at all organization levels and justify the utilities or benefits of integrating improvement initiatives.

/pdf/designing-a-strategic-measurement-program-for-software-x5mipcvcly.pdf

Designing a Strategic Measurement Program for Software Engineering Organizations: Discovering Difficulties and Problems

Automated software testing has proven its value for software development increasingly over the past few years. Software testing is an important phase in the entire software development process. There are various automated software testing tools are available today, which are used for testing various software applications whether it is desktop-based, mobile application, or a Web-based application. Evaluating a software testing tool is rather a subjective task, depending on the evaluator’s opinions rather than based on the objective approach. For this purpose, we have studied research papers, articles, journals, books, conference papers, few Web sites, etc., related with the study of software testing tools based on which we performed a survey of various automated software testing tools, i.e., Selenium, Watir, QTP, TestComplete, WinRunner, LoadRunner, SilkTest, Apache Jmeter, Wapt, Tellurium, Web Load, NeoLoad, LoadUI, Appvance, rational performance tester, SahiPro, Telerik Test Studio, Ranorex, Storm, Soap UI, TestNG, FitNese, Xebium, etc. The purpose of this research work is to summarize the existing literature and to establish an overview of the existing automated software testing tool to benefit the practice of users and for future research. We are attempting to provide detailed insight into automated software testing tools which can help the tester to choose the tool most suited to test his/her application.

A Systematic Literature Review of Automated Software Testing Tool

Software testing is an important part of any software development. With the emphasis on developing systems using modern object oriented technologies, a critically-sensitive issue arises in the area of testing. While traditional testing is reasonably well understood, object oriented testing presents a host of new challenges. This paper focuses on what differentiates the two in test cases, testing levels, and Object Oriented features affecting testing.

A Comparison of Software Testing Using the Object Oriented Paradigm and Traditional Testing

In this research paper, design a fault based testing tool based on their properties and it behavior (test cases for fault based testing) for software development. A requirement specification for a FBT is established that would involve studying the feature set offered by existing software testing tools, along with their limitations. The requirement set thus developed will be capable of overcoming the limitations of the limited feature sets of existing software tools and will also contribute to the design of a fault based testing tool using class diagram that includes most of the features required for a software testing tool .

Design Fault Based Testing Using Test Case Generation Technique

Object-orientation has rapidly become accepted as the preferred paradigm for large-scale system design. The product created during Software Development effort has to be tested since bugs may get introduced during its development. In this research work we 1) establish a requirement specification for a comprehensive software testing tool. 2) This will involve studying the feature set offered by existing software testing tools and their limitations. This will be able to overcome the limitations of limited feature sets of existing software tools. 3) To propose a comprehensive architecture of a software testing tool, this will include most of the features required for a software testing tool. 4) The purpose is to avoid compatibility problems which are incurred by interfacing various tools to utilize individual tools strengths. Also, as different tools are having different user interfaces, it takes effort to learn, how to use them. A full featured, comprehensive tool is a solution to all of these problems. We intend to propose the object oriented methodology based architectures for the comprehensive tool.

/pdf/a-full-featured-component-object-oriented-based-architecture-4f6jjqu1oh.pdf

A full featured component (object oriented) based architecture testing tool

This paper describes one of the fundamental concepts of practical software measurement. The measurement information model provides a formal method for linking defined information needs to software engineering processes and products the can be measured. Developing a measurement plan for a particular project requires an instantiation of the measurement information model that is specific to the projects information needs the model serve as a primary resource throughout the measurement process, as its guide the planning and implementation of data collection and analysis activities.

Measurement of software using various construct in information model

In this research investigate, quality of software using comprehend our architecture testing model [34], with the help of object oriented characteristic relationship, using different software metrics. The objective of ‘Design Architectural Testing Tool’ is to facilitate a design that may contribute to the comprehensiveness of the software testing tool. In this research work first we try to draw an architecture of testing method based on their attribute nature and shows their relationship next phase will be applied testing (based on different software metrics) on each component and after testing we apply different statistical analysis for validation of our research work .

/pdf/validation-of-software-architecture-for-object-oriented-3r4zf964lz.pdf

Lalji Prasad

Papers

A full featured component (object oriented) based architecture testing tool

Measurement of software using various construct in information model

Validation of Software Architecture for Object-Oriented Testing using with the Facilitate Quality Attributes

A Systematic Literature Review of Automated Software Testing Tool

Design Architecture Class Diagram for A Comprehensive Testing Tool