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

A method for agile localization test

IP.com Disclosure Number: IPCOM000249267D
Publication Date: 2017-Feb-15
Document File: 4 page(s) / 72K

Publishing Venue

The IP.com Prior Art Database

Abstract

In software localization, testing is based on the deliverables that developer provided, which might include user stories, feature work items, or translation files. In current process, testers would monitor the work items development provided, once the work item status changed, tester would check if anything updated and perform the tests. That is inefficient since the status might not marked in time, and testers might not be able to get all the information from user story to understand the new feature, it might take extra effort on communication with development teams. The disclosure discloses a solution to efficiently track the deliverables, and based on the related user stories/work items to crawl the tests that have been performed for the same function. The test cases could be quickly developed and automated from the existed test assets could be leveraged from release to release.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

1

A method for agile localization test

In software localization, testing is based on the deliverables that developer provided, which might include user stories, feature work items, or translation files.

In current process, a list of work items from development team are provided to the test team in each sprint. The list would be monitored from time to time to see if there is any status change. And part of work items might not be the focused area in localization perspective. Testers need to filter out the area which need to be tested. When the work item is marked as done, testers would create test cases based on the work item content and tester's experience on the product. That is inefficient since the status might not marked in time, and testers might not be able to get all the information from user story to understand the new feature, it might take extra effort on communication with development teams.

It's time-consuming to monitor the 'real' development progress all the time (Not every developers update the progress in time); understand the spec through short description in user stories; compare the difference on translation files to find out the potential changed area.

Translation verification test is part of the localization process, that focuses on the new and changed strings. The new strings might be from brand new features or from existed user interfaces which have updates. Currently, there is not an efficient way to reuse existed test cases. For new strings, testers need to go through the work item list from development team to find out the new/changed features to map with those strings.

The disclosure discloses a solution to efficiently track the deliverables, and based on the related user stories/work items to crawl the tests that have been performed for the same function. The test cases could be quickly developed and automated from the existed test assets could be leveraged from release to release.

1. An agent is created to monitor the defined file groups to see if there is any string changes in code repository.

2. Developer associates a work item to check in the code. Based on the associated work item, the following scheme would be created. A crawler to

track the work item to g...