Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Using function testcase metadata to automaticaly spawn globalization recommendations/testcases

IP.com Disclosure Number: IPCOM000180556D
Original Publication Date: 2009-Mar-11
Included in the Prior Art Database: 2009-Mar-11
Document File: 3 page(s) / 111K

Publishing Venue

IBM

Abstract

This article provides a new way to assimilate Globalization testing information and help use that to create use cases/recommendations that teams can execute to comply with their Globalization Verification Test (GVT) requirements. This disclosure will use the content from the functional testcases and look for keywords that will issue flags/need for globalization testing in that area. Then using a repository of Globalization specific metadata, create globalization verification testcases and several other recommendations.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Using function testcase metadata to automaticaly spawn globalization recommendations/testcases

The main idea of this disclosure aims at using functional testing metadata and cross referencing that with the globalization standards repository to create "Globalized Testcases" recommendations that can be taken as is and executed as Globalization Verification Test (GVT) tests. The source for functional testing metadata can be a team room, word docs, test tracking tools, or any other testcase storage repositories. The GVT areas and standards are also stored in some repository. The metadata from the functional tests will be compiled in XML format and the data for GVT standards will also be generated Extensible Markup Language (XML) format. The metadata from functional testing will contain specific attributes that the GVT metadata can recognize and hence be able to change that testcase/use case so it can be used for verifying globalization requirements. The implementation can be done in many ways but the core idea lies in the unique usage of functional test data and being able to transform it for globalization testing.

There are several advantages of using this methodology such as:
1) Saves time and effort
2) Uses product specific metadata, which will result in relevant GVT recommendations
3) Could potentially be used for every product within IBM and enhance productivity and globalization compliance
4) Help identify more GVT areas in the product and hence greatly reducing defects found during Translation Verification Testing (TVT)
5) Possibly also create plug-in for automated functional tests to auto spawn...