US9594749B2 - Visually differentiating strings for testing - Google Patents

Visually differentiating strings for testing Download PDF

Info

Publication number
US9594749B2
US9594749B2 US14/503,373 US201414503373A US9594749B2 US 9594749 B2 US9594749 B2 US 9594749B2 US 201414503373 A US201414503373 A US 201414503373A US 9594749 B2 US9594749 B2 US 9594749B2
Authority
US
United States
Prior art keywords
data string
localization
data
string
status
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US14/503,373
Other languages
English (en)
Other versions
US20160092440A1 (en
Inventor
Shiva Kavindpadi Bhuvaneswaran
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Microsoft Technology Licensing LLC
Original Assignee
Microsoft Technology Licensing LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Assigned to MICROSOFT CORPORATION reassignment MICROSOFT CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BHUVANESWARAN, SHIVA KAVINDPADI
Priority to US14/503,373 priority Critical patent/US9594749B2/en
Application filed by Microsoft Technology Licensing LLC filed Critical Microsoft Technology Licensing LLC
Assigned to MICROSOFT TECHNOLOGY LICENSING, LLC reassignment MICROSOFT TECHNOLOGY LICENSING, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICROSOFT CORPORATION
Priority to CN201580052896.0A priority patent/CN106716398B/zh
Priority to PCT/US2015/052759 priority patent/WO2016053920A1/en
Priority to EP15781236.3A priority patent/EP3201794A1/en
Publication of US20160092440A1 publication Critical patent/US20160092440A1/en
Priority to US15/426,771 priority patent/US10216727B2/en
Publication of US9594749B2 publication Critical patent/US9594749B2/en
Application granted granted Critical
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G06F17/2836—
    • G06F17/2854—
    • G06F17/289—
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/40—Processing or translation of natural language
    • G06F40/42—Data-driven translation
    • G06F40/47—Machine-assisted translation, e.g. using translation memory
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/40—Processing or translation of natural language
    • G06F40/51—Translation evaluation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/40—Processing or translation of natural language
    • G06F40/58—Use of machine translation, e.g. for multi-lingual retrieval, for server-side translation for client devices or for real-time translation
    • G06F9/4448—
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/451—Execution arrangements for user interfaces
    • G06F9/454—Multi-language systems; Localisation; Internationalisation

Definitions

  • a data string is a set of characters.
  • a computing device may implement a software application based upon the data string. Alternately, the computing device may present the data string to a user.
  • a data string may be translated from an original language to a localization language.
  • a localization language is the language native to the location containing the computing device. For example, a coder may compose a data string written in English. A computing device located in Japan may store the data string. The coder may localize the string to Japanese for easier consumption by a user.
  • Embodiments discussed below relate to using a color-coding system, or other visual marker, to indicate which data strings are ready for testing.
  • the data string test system may calculate a localization test status of a data string.
  • the data string test system may apply a visual marker of the localization test status of the data string to the data string.
  • the data string test system may present the visual marker and the data string to a user.
  • FIG. 1 illustrates, in a block diagram, one embodiment of a string management system.
  • FIG. 2 illustrates, in a block diagram, one embodiment of a computing device.
  • FIG. 3 illustrates, in a block diagram, one embodiment of a hash identifier generation.
  • FIG. 4 illustrates, in a block diagram, one embodiment of a data string record.
  • FIG. 5 illustrates, in a block diagram, one embodiment of a data string test user interface.
  • FIG. 6 illustrates, in a flowchart, one embodiment of a method of marking a string for testing.
  • FIG. 7 illustrates, in a flowchart, one embodiment of a method of determining a change status.
  • FIG. 8 illustrates, in a flowchart, one embodiment of a method of determining a localization status.
  • FIG. 9 illustrates, in a flowchart, one embodiment of a method of marking a string for testing using color-coding.
  • FIG. 10 illustrates, in a flowchart, one embodiment of a method of marking a string for testing using polygons.
  • the implementations may be a machine-implemented method, a tangible machine-readable medium having a set of instructions detailing a method stored thereon for at least one processor, or a data string test system.
  • a data string test system may generate a hash value for a data string of a software application to identify the data string.
  • the data string test system may append the hash value to the value of the string.
  • the hash value may be six hexadecimal digits suffixed by an underscore.
  • a hash locale may contain the data string prefixed by the hash value. When the software application is rendered in the hash locale, the data string and hash identifier may be visibly displayed.
  • the hash value may identify a resource path, a resource identifier, and a resource value for the hash.
  • the data string test system may identify a data string that has been changed. By recording each entry in for the current hash values not among the previous hash values, the data string test system may compile a list of hash values for data strings that were modified or added to the product, determining a change status for the data string.
  • the data string test system may compile a list of data strings that have not been translated to a local language, or “localized”.
  • the data string test system may compare a current list of untranslated data strings to a previous list of untranslated data strings to identify data strings that were translated in the recent product build, determining a localization status for the data string.
  • the data string test system may use the change status and the localization status to determine a localization test status, indicating whether a data string is ready to be localization tested. Localization testing checks the quality of the localization of a data string for a particular target locale or culture.
  • the data string test system may apply a visual marker to a data string when presenting that data string to the user to indicate the localization test status. A visual marker is overlaid atop the data string, rather than inherently changing the data string. A user may use the visual marker to identify quickly a data string for testing.
  • a data string test system may use a color-coding system, or other visual marker, to indicate which data strings are ready for testing.
  • the data string test system may calculate a localization test status of a data string.
  • the data string test system may apply a visual marker of the localization test status of the data string to the data string.
  • the data string test system may present the visual marker and the data string to a user.
  • FIG. 1 illustrates, in a block diagram, one embodiment of a data string management system 100 .
  • a string resource 110 may be a data file used to generate a data string as part of a software application.
  • the data string management system 100 may store a data string generated from the string resource 110 in a hash locale 120 .
  • the data string management system 100 may provide the data string to a translator for translation to a local language, referred to as “localization”.
  • the translator may be a translation program 130 or a human translator.
  • a translation program may translate the data string using auto-translation or machine translation. Auto-translation uses previously existing translations to translate the data string. Machine translation translates the data string on a word-by-word basis.
  • the translation program 130 may provide a translation of the data string as well as a confidence score, indicating the probability that the translation is accurate.
  • the translation program 130 may send the translation of the data string to a localization service provider (LSP) 140 for review and possible revision.
  • LSP localization service provider
  • a localization service provider 140 translates the data string into a local language.
  • the translation program 130 may send each translated data string to the localization service provider 140 or just the translated data strings with a confidence score below an automatic review threshold. Once the data string has been approved by the localization service provider 140 , the localization service provider 140 may set a localization flag on the data string indicating that the data string has been localized. Alternately, the translation program 130 may set the localization flag if the confidence score is above a specific confidence threshold. The localization service provider 140 may send the data string to a data string test system 150 for testing.
  • the confidence threshold may be pre-set, or set by the localization service provider 140 or the data string test system 150 .
  • the data string test system 150 may identify a data string for various types of testing.
  • FIG. 2 illustrates a block diagram of an exemplary computing device 200 which may act as a data string test system 150 .
  • the computing device 200 may combine one or more of hardware, software, firmware, and system-on-a-chip technology to implement a data string test system 150 .
  • the computing device 200 may include a bus 210 , a processor 220 , a memory 230 , a data storage 240 , an input device 250 , an output device 260 , and a communication interface 270 .
  • the bus 210 or other component interconnection, may permit communication among the components of the computing device 200 .
  • the processor 220 may include at least one conventional processor or microprocessor that interprets and executes a set of instructions.
  • the memory 230 may be a random access memory (RAM) or another type of dynamic data storage that stores information and instructions for execution by the processor 220 .
  • the memory 230 may also store temporary variables or other intermediate information used during execution of instructions by the processor 220 .
  • the data storage 240 may include a conventional ROM device or another type of static data storage that stores static information and instructions for the processor 220 .
  • the data storage 240 may include any type of tangible machine-readable medium, such as, for example, magnetic or optical recording media, such as a digital video disk, and its corresponding drive.
  • a tangible machine-readable medium is a physical medium storing machine-readable code or instructions, as opposed to a signal.
  • the data storage 240 may store a set of instructions detailing a method that when executed by one or more processors cause the one or more processors to perform the method.
  • the data storage 240 may also be a database or a database interface for storing a data string and associated metadata.
  • the input device 250 may include one or more conventional mechanisms that permit a user to input information to the computing device 200 , such as a keyboard, a mouse, a voice recognition device, a microphone, a headset, a touch screen 252 , a touch pad 254 , a gesture recognition device 256 , etc.
  • the output device 260 may include one or more conventional mechanisms that output information to the user, including a display screen 262 , a printer, one or more speakers 264 , a headset, or a medium, such as a memory, or a magnetic or optical disk and a corresponding disk drive.
  • the communication interface 270 may include any transceiver-like mechanism that enables computing device 200 to communicate with other devices or networks.
  • the communication interface 270 may include a network interface or a transceiver interface.
  • the communication interface 270 may be a wireless, wired, or optical interface.
  • the computing device 200 may perform such functions in response to processor 220 executing sequences of instructions contained in a computer-readable medium, such as, for example, the memory 230 , a magnetic disk, or an optical disk. Such instructions may be read into the memory 230 from another computer-readable medium, such as the data storage 240 , or from a separate device via the communication interface 260 .
  • a computer-readable medium such as, for example, the memory 230 , a magnetic disk, or an optical disk.
  • Such instructions may be read into the memory 230 from another computer-readable medium, such as the data storage 240 , or from a separate device via the communication interface 260 .
  • FIG. 3 illustrates, in a block diagram, one embodiment of a hash identifier generation 300 .
  • Each data string may have a hash identifier 310 to identify that data string.
  • the hash identifier 310 may be generated during run-time by a data string management system 100 , a data string test system 150 , or a computing device 200 operating a software application.
  • the data string test system 150 may generate a hash identifier based on attributes of the data string resource 110 .
  • the data string test system 150 may execute a hash function 320 to generate the hash identifier 310 .
  • the data string test system 150 may use a resource file 330 , a resource identifier 340 , and a resource value 350 as inputs for the hash function 320 .
  • a resource file 330 may describe a relative storage path of the data string resource 110 .
  • a resource identifier 340 may identify the data string resource 110 within the resource file 330 .
  • a resource value 350 may be the value stored at the data string resource 110 .
  • the data string test system 150 may adjust the hash function 320 to avoid repetition of hash identifiers 310 .
  • the hash identifier 310 may be stored with the data string and other data string metadata as part of a data string record 400 .
  • FIG. 4 illustrates, in a block diagram, one embodiment of a data string record 400 .
  • the data string record 400 may be stored in an extensible markup language (XML) format.
  • the data string record 400 may have a hash identifier field 410 to store the hash identifier 310 .
  • the data string record 400 may have a string field 420 to store the data string.
  • the data string record 400 may have a translation field 430 to store a translated version of the data string into a local language.
  • the data string record 400 may have a language identifier field 440 identifying the local language 440 .
  • the data string record 400 may have a confidence score field 450 to store a confidence score indicating the probability that the translation is accurate.
  • the data string record 400 may have a localization flag 460 indicating that the data string has been translated to a local language.
  • the data string record 400 may have a string error history 470 describing any previous errors that have occurred involving the data string.
  • the data string may have caused the errors or just may be involved tangentially.
  • the data string test system 150 may use this information to alert a user to the likelihood of an error being present.
  • FIG. 5 illustrates, in a block diagram, one embodiment of a data string test user interface 500 .
  • the data string test system 150 may use the data string test user interface 500 to present a set of one or more data strings to a user.
  • the data string test user interface 500 may display the set of one or more data strings 510 to the user on a display screen 262 .
  • the user may select one or more data strings 510 from the displayed set of data strings 510 to test.
  • the user may select a data string 510 that has been altered since the last test and has been localized.
  • the data string test user interface 500 may use a visual marker to identify a data string 510 that is a candidate for testing.
  • a past test visual marker 512 may indicate that the data string 510 is unchanged since the last time the data string 510 was tested.
  • a present test visual marker 514 may indicate that the data string 510 has been altered since the last time the data string 510 was tested and that the data string 510 has been localized since the data string 510 changed.
  • a future test visual marker 516 may indicate that the data string 510 has been altered since the last time the data string 510 was tested but has not been localized.
  • the visual marker may be a color-coding for the data string 510 that changes the color of the text of the data string 510 .
  • the data string test system 150 may color-code a data string 510 that has been changed and localized, and is, thus, ready for testing in green.
  • the data string test system 150 may color-code a data string 510 that has already been tested since the last change to the data string 510 in blue.
  • the data string test system 150 may color-code a data string 510 that has been changed but has not yet been localized in red, indicating that the data string 510 is not yet ready for testing.
  • the visual marker may be a framing polygon that frames the data string 510 .
  • the data string test system 150 may frame a data string 510 that has been changed and localized, and is, thus, ready for testing with an arrow.
  • the data string test system 150 may frame a data string 510 that has already been tested since the last change to the data string 510 with a box.
  • the data string test system 150 may frame a data string 510 that has been changed but has not yet been localized with an octagon, indicating that the data string 510 is not yet ready for testing.
  • FIG. 6 illustrates, in a flowchart, one embodiment of a method 600 of marking a string for testing.
  • the data string test system 150 may associate a string error history 470 with the data string 510 (Block 602 ).
  • the data string test system 150 may determine a change status of the data string 510 (Block 604 ).
  • the data string test system 150 may determine a localization status of the data string 510 (Block 606 ).
  • the data string test system 150 may calculate a localization test status of the data string 510 based on the change status and the localization status (Block 608 ).
  • the data string test system 150 may apply a visual marker of the localization test status to the data string 510 (Block 610 ).
  • the data string test system 150 may alter a secondary characteristic of the visual marker to indicate at least one of a string error history, a string context, or other data indicating the likelihood that an error is present (Block 612 ).
  • the data string test system 150 may present the visual marker and the data string 510 to a user (Block 614 ).
  • the data string test system 150 may reset the visual marker once the data string 510 has been selected for testing (Block 616 ).
  • FIG. 7 illustrates, in a flowchart, one embodiment of a method 700 of determining a change status.
  • the data string test system 150 may identify that a build has occurred, possibly changing some data strings 510 (Block 702 ).
  • the data string test system 150 may generate a hash identifier 320 for the data string 510 based on at least one of a resource file 330 , a resource identifier 340 for the data string 510 , and a resource value 350 for the data string 510 (Block 704 ).
  • the data string test system 150 may append the hash identifier 320 to the data string 510 (Block 706 ).
  • the data string test system 150 may compare a current build version of the hash identifier of the data string 510 to a previous build version of the hash identifier 320 (Block 708 ). If the current build version of the hash identifier 320 matches the previous build version of the hash identifier 320 (Block 710 ), the data string test system 150 may designate the data string 510 as unchanged (Block 712 ). If the current build version of the hash identifier 320 does not match the previous build version of the hash identifier 320 (Block 710 ), the data string test system 150 may designate the data string 510 as having changed (Block 714 ).
  • FIG. 8 illustrates, in a flowchart, one embodiment of a method 800 of determining a localization status.
  • the data string test system 150 may append a localization flag to a data string (Block 802 ). If the data string test system 150 detects that the data string has not been localized for an error period (Block 804 ), the data string test system 150 may alert a user to analyze a potential lack of localization or a hardcode bug (Block 806 ).
  • An error period is a minimum amount of time that a data string may go without a localization after a change has occurred as determined by a tester or other administrator.
  • the data string test system 150 may alert the user to localize the data string by altering a characteristic of the visual marker. For example, the data string 510 may be color-coded a flashing red.
  • the data string test system 150 may receive a translated version 430 of the data string 510 from a translation program 130 (Block 808 ).
  • the data string test system 150 may receive a confidence score 450 for the translated version of the data string 510 from the translation program 130 (Block 810 ).
  • the data string test system 150 may compare the confidence score 450 to a confidence threshold (Block 812 ). If the confidence score 450 passes the confidence threshold (Block 814 ), the data string test system may set the localization flag 460 when the confidence score 450 for a translated version of the data string 510 passes the confidence threshold (Block 816 ).
  • the data string test system 150 may provide access to a localization service provider 140 to revise a translated version of the data string 510 (Block 818 ).
  • FIG. 9 illustrates, in a flowchart, one embodiment of a method 900 of marking a data string 510 for testing using color-coding.
  • the data string test system 150 may associate a string error history 470 with the data string 510 (Block 902 ).
  • the data string test system 150 may determine a change status of the data string 510 to calculate the localization test status (Block 904 ).
  • the data string test system 150 may determine a localization status of the data string 510 to calculate the localization test status (Block 906 ).
  • the data string test system 150 may calculate a localization test status of the data string 510 based on the change status and the localization status (Block 908 ).
  • the data string test system 150 may apply a color-coding to the data string 510 as a visual marker indicating a localization test status of the data string 510 (Block 910 ).
  • the data string test system 150 may adjust a hue of the color-coding to indicate at least one of a string error history, a string context, or other data indicating the likelihood that an error is present (Block 912 ).
  • the data string test system 150 may present the data string 510 with the color-coding to a user (Block 914 ).
  • the data string test system 150 may reset the visual marker once the data string 510 has been selected for testing (Block 916 ).
  • FIG. 10 illustrates, in a flowchart, one embodiment of a method 1000 of marking a data string 510 for testing using polygons.
  • the data string test system 150 may associate a string error history 470 with the data string 510 (Block 1002 ).
  • the data string test system 150 may determine a change status of the data string 510 (Block 1004 ).
  • the data string test system 150 may determine a localization status of the data string 510 (Block 1006 ).
  • the data string test system 150 may calculate a localization test status of the data string 510 based on the change status and the localization status (Block 1008 ).
  • the data string test system 150 may frame the data string 510 with a framing polygon as a visual marker indicating a localization test status of the data string 510 (Block 1010 ).
  • the data string test system 150 may alter the shape of the framing polygon to indicate at least one of a string error history, a string context, or other data indicating the likelihood that an error is present (Block 1012 ).
  • the data string test system 150 may present the data string 510 with the framing polygon to a user (Block 1014 ).
  • the data string test system 150 may reset the visual marker once the data string 510 has been selected for testing (Block 1016 ).
  • Embodiments within the scope of the present invention may also include computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon.
  • Such computer-readable storage media may be any available media that can be accessed by a general purpose or special purpose computer.
  • Such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic data storages, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures. Combinations of the above should also be included within the scope of the computer-readable storage media.
  • Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network.
  • Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
  • Computer-executable instructions also include program modules that are executed by computers in stand-alone or network environments.
  • program modules include routines, programs, objects, components, and data structures, etc. that perform particular tasks or implement particular abstract data types.
  • Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Artificial Intelligence (AREA)
  • Human Computer Interaction (AREA)
  • Debugging And Monitoring (AREA)
US14/503,373 2014-09-30 2014-09-30 Visually differentiating strings for testing Active US9594749B2 (en)

Priority Applications (5)

Application Number Priority Date Filing Date Title
US14/503,373 US9594749B2 (en) 2014-09-30 2014-09-30 Visually differentiating strings for testing
CN201580052896.0A CN106716398B (zh) 2014-09-30 2015-09-29 可视地区分用于测试的字符串
EP15781236.3A EP3201794A1 (en) 2014-09-30 2015-09-29 Visually differentiating strings for testing
PCT/US2015/052759 WO2016053920A1 (en) 2014-09-30 2015-09-29 Visually differentiating strings for testing
US15/426,771 US10216727B2 (en) 2014-09-30 2017-02-07 Visually differentiating strings for testing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US14/503,373 US9594749B2 (en) 2014-09-30 2014-09-30 Visually differentiating strings for testing

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/426,771 Continuation US10216727B2 (en) 2014-09-30 2017-02-07 Visually differentiating strings for testing

Publications (2)

Publication Number Publication Date
US20160092440A1 US20160092440A1 (en) 2016-03-31
US9594749B2 true US9594749B2 (en) 2017-03-14

Family

ID=54325712

Family Applications (2)

Application Number Title Priority Date Filing Date
US14/503,373 Active US9594749B2 (en) 2014-09-30 2014-09-30 Visually differentiating strings for testing
US15/426,771 Active US10216727B2 (en) 2014-09-30 2017-02-07 Visually differentiating strings for testing

Family Applications After (1)

Application Number Title Priority Date Filing Date
US15/426,771 Active US10216727B2 (en) 2014-09-30 2017-02-07 Visually differentiating strings for testing

Country Status (4)

Country Link
US (2) US9594749B2 (zh)
EP (1) EP3201794A1 (zh)
CN (1) CN106716398B (zh)
WO (1) WO2016053920A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10216727B2 (en) 2014-09-30 2019-02-26 Microsoft Technology Licensing, Llc Visually differentiating strings for testing

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9792282B1 (en) * 2016-07-11 2017-10-17 International Business Machines Corporation Automatic identification of machine translation review candidates
US10162819B2 (en) 2016-08-17 2018-12-25 Netflix, Inc. Change detection in a string repository for translated content
CN108509117A (zh) * 2017-02-27 2018-09-07 腾讯科技（深圳）有限公司 数据显示方法及装置
US10489513B2 (en) 2017-04-19 2019-11-26 Salesforce.Com, Inc. Web application localization
US10437935B2 (en) 2017-04-18 2019-10-08 Salesforce.Com, Inc. Natural language translation and localization
CA3002052C (en) * 2017-04-18 2023-08-29 Salesforce.Com, Inc. Natural language translation and localization
US10795799B2 (en) 2017-04-18 2020-10-06 Salesforce.Com, Inc. Website debugger for natural language translation and localization
US11630681B2 (en) * 2019-09-10 2023-04-18 Microsoft Technology Licensing, Llc Integrated system for localization of resources tailored for translations by setting a flag
CN112765039B (zh) * 2021-02-03 2022-05-06 上海复深蓝软件股份有限公司 测试数据消费染色方法、装置、计算机设备及存储介质
CN113138933A (zh) * 2021-05-13 2021-07-20 网易（杭州）网络有限公司 数据表的测试方法、电子设备及存储介质

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1202168A2 (en) 2000-10-30 2002-05-02 Microsoft Corporation System and method for dynamically veryfying the compatibility of a user interface resource
US20030115552A1 (en) 2001-11-27 2003-06-19 Jorg Jahnke Method and system for automatic creation of multilingual immutable image files
US20090282394A1 (en) 2008-05-12 2009-11-12 Ca, Inc. Product localization device and method
US20090307365A1 (en) * 2003-03-11 2009-12-10 Research In Motion Limited Localization Of Resources Used By Applications In Hand-Held Electronic Devices And Methods Thereof
US20100023319A1 (en) * 2008-07-28 2010-01-28 International Business Machines Corporation Model-driven feedback for annotation
US7797349B2 (en) 2007-03-06 2010-09-14 Kyocera Mita Corporation Device user interface XML string table manager
US20100262660A1 (en) * 2009-04-08 2010-10-14 Research In Motion Limited Method, system and mobile device for implementing a serverless presence system
US20130223680A1 (en) * 2012-02-24 2013-08-29 Toshiba Tec Kabushiki Kaisha Recognition system, recognition method and computer readable medium
US20130326323A1 (en) * 2012-05-30 2013-12-05 Google Inc. Systems and methods for displaying contextual revision history
US8612893B2 (en) 2009-06-10 2013-12-17 Microsoft Corporation Dynamic screentip language translation
US20140172411A1 (en) * 2012-12-17 2014-06-19 Electronics And Telecommunications Research Institute Apparatus and method for verifying context

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9916306B2 (en) * 2012-10-19 2018-03-13 Sdl Inc. Statistical linguistic analysis of source content
US20150242512A1 (en) * 2012-12-11 2015-08-27 Google Inc. Systems and Methods for Ranking Search Results Based on User Identification of Items of Interest
US9594749B2 (en) 2014-09-30 2017-03-14 Microsoft Technology Licensing, Llc Visually differentiating strings for testing

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1202168A2 (en) 2000-10-30 2002-05-02 Microsoft Corporation System and method for dynamically veryfying the compatibility of a user interface resource
US20030115552A1 (en) 2001-11-27 2003-06-19 Jorg Jahnke Method and system for automatic creation of multilingual immutable image files
US20090307365A1 (en) * 2003-03-11 2009-12-10 Research In Motion Limited Localization Of Resources Used By Applications In Hand-Held Electronic Devices And Methods Thereof
US8037199B2 (en) 2003-03-11 2011-10-11 Research In Motion Limited Localization of resources used by applications in hand-held electronic devices and methods thereof
US7797349B2 (en) 2007-03-06 2010-09-14 Kyocera Mita Corporation Device user interface XML string table manager
US20090282394A1 (en) 2008-05-12 2009-11-12 Ca, Inc. Product localization device and method
US20100023319A1 (en) * 2008-07-28 2010-01-28 International Business Machines Corporation Model-driven feedback for annotation
US20100262660A1 (en) * 2009-04-08 2010-10-14 Research In Motion Limited Method, system and mobile device for implementing a serverless presence system
US8612893B2 (en) 2009-06-10 2013-12-17 Microsoft Corporation Dynamic screentip language translation
US20130223680A1 (en) * 2012-02-24 2013-08-29 Toshiba Tec Kabushiki Kaisha Recognition system, recognition method and computer readable medium
US20130326323A1 (en) * 2012-05-30 2013-12-05 Google Inc. Systems and methods for displaying contextual revision history
US20140172411A1 (en) * 2012-12-17 2014-06-19 Electronics And Telecommunications Research Institute Apparatus and method for verifying context

Non-Patent Citations (11)

* Cited by examiner, † Cited by third party
Title
"International Search Report and Written Opinion Issued in PCT Application No. PCT/US2015/052759", Mailed Date: Feb. 9, 2016, 11 pages.
"Localization Checklist", Available at: <<https://developerandroid.com/distribute/tools/localization-checklist.html#manage-strings>>, Jul. 6, 2014, 8 Pages.
"Localization Checklist", Available at: >, Jul. 6, 2014, 8 Pages.
"Localization", Available at: <<http://developer.blackberry.com/native/documentation/cascades/device-platform/internationalization/localization.html, Retrieved on: Aug. 4, 2014, 6 Pages.
"Localization", Available at: http://kitsune.readthedocs.org/en/latest/localization.htunl#testing-localized-strings, Oct. 23, 2013, 13 Pages.
"Testing Your Internationalized App", Available at: <<https://developer.apple.com/library/prerelease/ios/documentation/MacOSX/Conceptual/BPInternational/TestingYourInternationalApp/TestingYourInternationalApp.html>>, Jun. 3, 2014, 4 Pages.
"Visual Localizer", Available at: <<http://visuallocalizer.codeplex.com/documentation>>, Nov. 1, 2013, 6 Pages.
"Visual Localizer", Available at: >, Nov. 1, 2013, 6 Pages.
PCT International 2nd Written Opionion in PCT/2015/052759, mailed Aug. 18, 2016, 6 pages.
Reynaud, Claire, "Getting your iPhone App Ready for Localization", Available at: <<https://www.clairereynaud.net/blog/getting-your-iphone-app-ready-for-localization/, Nov. 21, 2013, 11 Pages.
Safar, et al., "Best Practices in Localization Testing", In Journal of Multilingual, vol. 21, Issue 1, Jan. 2010, 5 Pages.

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10216727B2 (en) 2014-09-30 2019-02-26 Microsoft Technology Licensing, Llc Visually differentiating strings for testing

Also Published As

Publication number Publication date
US20170147562A1 (en) 2017-05-25
CN106716398A (zh) 2017-05-24
US10216727B2 (en) 2019-02-26
CN106716398B (zh) 2020-03-03
WO2016053920A1 (en) 2016-04-07
US20160092440A1 (en) 2016-03-31
EP3201794A1 (en) 2017-08-09

Similar Documents

Publication Publication Date Title
US10216727B2 (en) Visually differentiating strings for testing
US9934129B1 (en) Determining application test results using screenshot metadata
US10606739B2 (en) Automated program code analysis and reporting
US10248537B2 (en) Translation bug prediction classifier
US8627290B2 (en) Test case pattern matching
US10579346B2 (en) Mobile accessibility evaluation from application binary
US11144839B2 (en) Processing data for use in a cognitive insights platform
US10169188B2 (en) Runtime evaluation of user interfaces for accessibility compliance
US10140102B2 (en) Evaluating accessibility compliance of a hybrid user interface design
US10067860B2 (en) Defining test bed requirements
US11029981B2 (en) Text resources processing in an application
US9304893B1 (en) Integrated software development and test case management system
US10664267B2 (en) Automatically detecting feature mismatches between mobile application versions on different platforms
US20150261505A1 (en) Method and system for generating stateflow models from software requirements
US11861332B2 (en) String localization for universal use
US10229110B2 (en) Displaying an application in the graphical user interface of a computer display
US10664254B2 (en) Analyzing binary software components utilizing multiple instruction sets
WO2016189721A1 (ja) ソースコード評価装置及びソースコード評価方法及びソースコード評価プログラム
US20240012909A1 (en) Correction of non-compliant files in a code repository
JP2017207876A (ja) ダンプマスクプログラム、ダンプマスク方法、および情報処理装置
US20140067359A1 (en) Automated iterative error simulation
US11270083B2 (en) Obtaining translations utilizing test step and subject application displays
CN116302086A (zh) 应用程序的处理方法、装置、电子设备与可读存储介质
JP2014067170A (ja) 実行条件検査装置、実行条件検査システム、実行条件検査方法およびプログラム

Legal Events

Date Code Title Description
AS Assignment

Owner name: MICROSOFT CORPORATION, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BHUVANESWARAN, SHIVA KAVINDPADI;REEL/FRAME:033857/0950

Effective date: 20140926

AS Assignment

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034747/0417

Effective date: 20141014

Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:039025/0454

Effective date: 20141014

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8