Category: Testing & QA

Software testing, quality assurance, test automation

  • Building ALM Basic Testing: SAP ALM Fundamentals

    Building ALM Basic Testing — SAP Application Lifecycle Management Fundamentals.

    ALM encompasses the management and optimization of all phases of the software lifecycle. For SAP environments, this presents a special challenge due to the complexity and heterogeneity of the system.

    The basic testing component of an ALM framework for SAP must address:

    • Test case management: Structured documentation and versioning of test cases linked to business processes
    • Impact-based test selection: Determining the relevant test scope based on what has changed, rather than running all tests every time
    • Regression testing: Automated validation that existing functionality still works after changes
    • Defect tracking: Integration between test results, defects, and transport management

    A mature ALM Basic Testing setup reduces manual testing effort significantly while simultaneously increasing quality assurance coverage. beteo recommends establishing ALM Basic Testing as the foundation before building more advanced ALM capabilities.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • Building ALM Foundation Testing

    Application Lifecycle Management (ALM) encompasses the management and optimization of all phases of the software lifecycle. For SAP environments, this presents a particular challenge due to the complexity and heterogeneity of the system.

    The foundation of ALM in SAP environments rests on three pillars:

    1. Requirements Management: Clear documentation and traceability of business requirements from inception through implementation. In SAP contexts, this means linking functional requirements to specific customizing settings and ABAP development objects.

    2. Test Management: Structured, risk-based testing that covers both regression scenarios and new functionality. The testing scope must be intelligently derived from change impact analysis — testing everything is neither feasible nor economical.

    3. Transport Management: Controlled, consistent deployment of changes across the SAP system landscape. This requires automated consistency checks and dependency management to prevent the “overtaker transport” problems that plague many SAP operations.

    Building this ALM foundation is not a one-time project but an ongoing capability development. Organizations that invest systematically in ALM foundation capabilities see measurable improvements in deployment quality, reduced downtime, and lower total cost of ownership for their SAP landscapes.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • SAP Testing with HP Products — A Contradiction?

    SAP Testing with HP Products — A Contradiction and HP a Marriage of Convenience?

    It is striking how difficult SAP finds it to position itself as a reseller of HP software components.

    Considering the complexity and heterogeneity of SAP, it would actually seem obvious that the HP software suite is the ideal instrument for managing SAP.

    Conclusion: SAP and HP should absolutely work together to develop a strategy for providing a joint xApp for managing complex IT environments.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • SAP Testing with HP Products: A Contradiction?

    It is striking how difficult SAP finds it to position itself as a reseller of HP software components.

    Considering the complexity and heterogeneity of SAP, it would actually seem obvious that the HP software suite is the ideal instrument for managing SAP environments. SAP promotes its own Solution Manager as the central ALM platform, while HP offers a more comprehensive and mature testing toolset. This creates a tension for customers who must choose between tight SAP integration and superior testing capabilities.

    SAP and HP have established a partnership, but the integration between SAP’s own tools and HP’s testing and ALM suite remains fragmented. Customers who invest in HP Quality Center or HP LoadRunner for SAP testing often find that integration points are limited and require significant customization effort.

    Conclusion: SAP and HP should urgently work together to develop a joint strategy for providing a common solution for managing complex IT landscapes. Until then, customers need to carefully evaluate both options and implement integration solutions that bridge the gap between SAP-native tools and the HP software suite.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • HP Quality Center 10: From a Test Manager’s Perspective

    The new Version 10 of the HP Quality Center (QC) is now available. Yet what are the actual advantages of the new QC compared to its predecessor from a Test Manager’s perspective? Below, I will take a look at some of the new features and changes, and I will answer the question whether one should even make the switch.

    The Most Significant Changes:

    HP Quality Center 10 brings several important new features. The most significant change is the complete redesign of the user interface, which is now based on a web client rather than a dedicated client application. This brings advantages in terms of deployment and maintenance, but requires adaptation from experienced QC users.

    New features include improved dashboard functionality with customizable views and reports, better integration with HP’s ALM tool suite, enhanced defect workflow capabilities, and improved performance with large test repositories.

    From a Test Manager’s perspective, the most valuable improvements are in reporting and dashboard functionality. The new dashboards provide better real-time visibility into test execution status and defect trends. The improved reporting capabilities make it easier to create management-level reports that communicate test progress and quality status effectively.

    The migration from QC 9.x to QC 10 requires careful planning. Data migration needs to be tested thoroughly, and all integrations with other tools must be re-validated. Custom workflows and business rules need to be reviewed and potentially adapted for the new version.

    Recommendation: HP Quality Center 10 offers genuine improvements, particularly in reporting and dashboarding. However, the migration effort should not be underestimated. A phased migration approach with thorough testing is recommended.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • Integrating Jira and HP Quality Center

    Testing departments use HP Quality Center (QC) for quality management and testing activities. Besides managing test requirements, it also helps them to compile test plans, and to conduct and monitor testing. In addition, Quality Center gives them a way to manage all defect tracking.

    However, developers often work with their own tools to manage bugs and defects, and to monitor problem-fixes. This is often Jira, an issue tracking and project management tool from Atlassian. This creates a situation where two different tools are used for defect management: HP Quality Center on the testing side and Jira on the development side.

    The integration of Jira and HP Quality Center bridges this gap by synchronizing defects between the two tools. When a tester creates a defect in Quality Center, it can automatically be created in Jira as well. When a developer updates the status in Jira, the change is reflected in Quality Center. This bidirectional synchronization ensures that both teams always have access to the latest defect status.

    beteo has implemented such integrations for various clients and has developed expertise in the technical and organizational aspects of tool integration. The benefits include: elimination of duplicate data entry, improved communication between testing and development teams, better traceability from defects to fixes, and more accurate reporting across both tools.

    The integration can be implemented using various approaches, including commercial integration tools and custom development. The choice of approach depends on the specific requirements and the technical environment.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • Test Management – Much Quality for Little Money

    From my point of view, there are three key components for reaching the goal „high quality at low costs“ in test management: adequate methods, adequate staffing, and adequate tools – each at the  right time. If one of these factors are neglected, the  project threatens to fail.

    Luckily, the tool comes with the adequate method, without nailing you down too much, enabling the planning of resources and test phases. I have had some experience with projects where all team members started off highly motivated, applying well thought-out methods, but soon failed to come to grips with the tools – the  worst-case in general being a spread-sheet driven project, in which things like: „Haven´t you run a test? I made an entry in the Excel sheet that you should …. oh, sorry, it is still on my computer, forgot to upload it. …” typically happen.

    Another frequent scenario: the best of all tools has been installed, but nobody ever told the people to make use of it.

    So what should a tool be able to perform that is expected to map a consistent quality management process and make it transparent to all people involved? From my point of view, this tool should

    • provide a simple and intuitive interface,
    • enable global using, i.e. be web-based, without requiring much installation effort,
    • allow requirements to be recorded, categorized, and evaluated,
    • enable risk estimation,
    • allow rights and roles to be managed,
    • allow tasks to be assigned,
    • be able to have test cases recorded, managed, and executed,
    • enable simple release management,
    • allow errors to be recorded and traced in a workflow,
    • facilitate evaluation of the different phases as well as the total project,
    • be able to link all entities and allow detected errors to be assigned to a test case or a requirement,
    • enable test automation – by service tests in an early phase, later also by GUI automation,
    • have open interfaces to other tools.

    A high degree of acceptance by all persons involved should be achieved and the users should be able to apply the solution without too much training.

    Having read my article up to this point, you might think: Okay, I realize that Excel can´t do all this. But I wonder if any other tool can? In my opinion, there is one tool that meets these requirements, Quality Center by HP, originally launched by Mercury Interactive.

    And the best of all: Not only can I observe that it makes my quality and test management projects a success, I also take great pleasure in working with it.

    About the author:
    Gerd Fladrich ist test management expert at Fladrich Consulting, Pliening near München, a beteo partner in the  section of quality management and testing.

  • Is Tool-Supported Test Management Profitable?

    Every software project targets at providing high-quality software within the frame of a cost and time schedule. tool-based IT test management usually accompanies the whole software development process and partly adds to reaching this goal. This includes tasks like requirements management, test planning, test design, test execution, test evaluation as well as a superordinate defects management.

    Practical experience
    However, erratic and unsystemantic testing is general practice in many enterprises. A variety of manual steps, redundancies and inconsistent documentations are the order of the day, resulting in additional costs. On the other hand, high benefit could be achieved by use of a tool-based test management. Introducing the necessary test management tools, along with the suitable methods and processes, improves both the testing process and the software quality. The  benefit  provided for both the test organization and the IT projects can be summarized as follows:

    Testing gets

    • standardized (tool instead of free-text in Word/Excel), more systematic, more reliable,
    • less time-consuming, easier to execute,
    • verifiable (content and coverage), more effective and comprehensive,
    • traceable,
    • reusable, trainable,
    • it can be automated
    • and planned.

    Using test management methods and tools facilitates error recovery and consistently reduces error occurrence. Time and costs for testing and support are enormously reduced as well. This results in a reduction of total costs, higher quality, transpareny, improved system requirements and completion on schedule, if not ahead of schedule. Operation will be less error-prone with reduced breakdown frequency, leading to highest-possible customer satisfaction.

    The benefit is evident. The earlier an error is detected, the easier its recovery. But often, there is no time for testing, the project is behind schedule and people are under time pressure. Testing is considered a necessary evil. But tool-based test management is more than just a cost factor. If used in the right way, test management is a value-adding process.

    Potential return of tool-based test management
    Potential improvements are not easy to quantify. However, experience from successful implementations of the test management tool HP Quality Center has shown that real improvement is possible:

    • Improved product quality leading to
      • Less delay caused by bad product quality
      • Avoiding frequent emergency implementations during production
      • Higher customer satisfaction by meeting expected delivery requirements
      • Cost savings by less re-working and reduced support costs
    • Improved testing process leading to
      • Lower costs per test cycle by standardization and reuse
      • Standardization of planning, documentation and execution of tests
      • Less time and cost effort for preparation thanks to reuse of requirements, testing data and test cases
      • Fast test execution by automated regression testing
    • Improved use of test resources leading to
      • Savings by centralized use of HP Quality Center (hardware, software, support, services)
      • Automated test coverage management avoids the need for retesting or performing unneeded testing
    • Improved project delivery leading to
      • More predictable and optimizated delivery schedule
      • Test automation, less time needed for execution, reduced use of resources
      • Optimized use of project resources, e.g. by higher performance, better prioritization
      • Test resources are earlier made available to new projects (by on schedule delivery)
      • Comparable results allowing to continously improve test processes

    The aspects of potential benefit listed above can be used as a basis for profit calculation. By applying a scoping approach to the project, the relevant data and facts can be derived from above general potential advantages and applied to the particular environment, and the actual return can be calculated.

    Summary
    Test management is necessary and clearly improves the quality of software projects. The advantages of tool-based test management are evident. However, it is not always easy to quantify and clearly define the benefit. Often, a budget for testing projects is approved only after some unpleasant incident has happened. This can be avoided, though.

    Successful implementations of the test management tool HP Quality Center have shown that practical improvements can definitely be realized and the de facto profit can be calculated in advance. The general aspects of potential value can easily be transferred to the particular environment by applying project scoping. Data and facts gained then form the basis of a specific profit calculation. Tool-supported test management does not only pay off, but the benefit can also be quantified.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • E2E SAP Testing – Halfway Under Control?

    In many blogs, we have discussed the deficiencies in SAP testing. Changes to an existing system are the order of the day. Again and again, errors are corrected, customizing and programs must be adapted, new functions are rolled out. Also, technical changes as hot fixes and service packs must be installed, as well as upgrades. In view of the large number of changes, problems with testing is not want you really want. But most SAP customers have come to terms with it, solving retroactively the problems involved with rolling out badly or incompletely tested changes – amidst the applause of the business. This is quite an effort, but still considered a more sensible approach than testing the whole software system.

    Everyone will agree that this is not the approach we want. Fortunately, specialized consulting companies such as FocusFrame as well as manufacturers of testing software such as HP,  Panaya, IntelliCorp, IBIS and above all SAP have taken this to heart. However, we are still far from a real end-to-end (E2E) testing or quality process starting right from the business requirements level, but at least you can start a continuous E2E testing process covering all changes as soon as the transport of a SAP change request is due. And this is already a great benefit.

    What Does This Mean in Detail?

    SAP E2E testing process and tools

    • The first step is to analyze which SAP transactions and programs are affected by the change, on the basis of the changes due for transport and of the system or a model of it. This step is mostly referred to as Change Impact Testing. This task is supported by specialized products like HP Change Impact Testing (CIT) for SAP, SAP Test Automation and Optimization (SAP TAO) as well as IntelliCorp LiveCompare. An exciting alternative is Panaya Inc.´s pure SaaS solution. Using this service, the SAP user does not even have to install any software.
    • Once the involved transactions are known, it must be found out which testing scenarios are necessary. For this step, too, there is reasonable technical support now. As a result, the testing scenarios are identified and together with the underlying test script made available to the test management tool. This is accomplished by using SAP Test Automization and Optimization in combination with SAP Quality Center by HP.
    • In spite of above system support and test szenario reduction, the testing scenarios should – due to their large number – pass another filter. This step is widely referred to as Risk Based Testing. The point here is to reduce the number of tests to be executed to the really relevant ones. This step is supported by SAP TAO and, particularly, by SAP Quality Center by HP.
    • Then, the test management tool executes the filtered tests automatically. The results are evaluated and, if necessary, the defect management process is started and monitored. This task is assumed by SAP Quality Center by HP in combination with HP Quick Test Pro.

    From Transport Packet-to-End-Testing up to real E2E Testing
    All this sounds quite simple and logical. In practice, however, it is quite a challenge to set up and operate such an environment. As a methodologist, however, you will consider this „reactive“ approach still suboptimal as the above „E2E“ quality process, instead of starting from the beginning, meaning the requirements management, is initiated not before the changes have been executed and ready for transport. Information about the effects of changes is known to be useful on starting the projects from the project portfolio management, supporting the business analyst as well as the developers and the test team. SAP has become aware of this and is working on a solution using the new Business Process Change Analyzer (SAP BPCA) to enable real E2E quality management.

    Implementing SAP E2E testing correctly will change the poor SAP E2E quality mangement into a model for other commercial software solutions addressing quality management. The benefit of a consistent, comprehensive testing for SAP landscapes can hardly be overestimated. The reduced number of system breakdowns after the weekly roll-out of changes justifies the investment in this area – as every head of a SAP Competence Center will readily confirm. The somewhat less spectacular quality improvement along with the cost and risk reduction reached in the medium term, will provide a considerable profit by introducing a SAP E2E testing project in the context of an application lifecycle management initiative.

    🇩🇪 Diesen Beitrag auf Deutsch lesen

  • Forrester: HP is Number 1 for Functional Testing

    According to then most recent Forrester Wave Report dating July 8, 2008 on Functional Testing solutions HP clearly keeps on leading this market.

    Using 96 criteria Forrester evaluated 6 solutions and came to clear results:

    • HP continues leading the functional testing market since it acquired Mercury Interactive in 2006.
    • IBM has a very promising product roadmap and has expanded its support for packaged applications.
    • Borland Software and Compuware reinforced their position with their respective users – Borland for the more technical testers, Compuware fot the less technical.
    • Empirix‘ and Seapine Software’s offers are less-costly but also functionally less-capable mainly because of limited support for applications and technologies.

    Overall Forrester observed functional testing solutions not only keeping up with new technologies but also improving functionality for manual testing, test management and test automation.

    Forrester Research evaluated the the most recent available versions of the following functional testing offerings:

    🇩🇪 Diesen Beitrag auf Deutsch lesen