[EXCONTRANS-270] Test connection successful despite of wrong Project Code in config Created: 12/Jul/18  Updated: 23/Jul/18  Resolved: 17/Jul/18

Status: Closed
Project: Content Translation Extended (CTX)
Component/s: Translations.com Translator
Affects Version/s: 2.0
Fix Version/s: 2.0

Type: Bug Priority: Major
Reporter: Gourav Assignee: Chuong Doan Huy
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 1d 6.5h
Original Estimate: Not Specified
Environment:

Demo Instance


Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Test connection on Edit Batch Page is getting successful even if translation config has wrong PD Project code.

 

Expected:

Test connection should validate following parameters from config:

  • URL
  • Username
  • Password
  • PD Projects assigned to user
  • PD Project short code
  • Source language
  • Target languages

 

if all these checks passed then only display Connection successful message to user otherwise log appropriate reason for connection failure in logs for further debugging.

 

 



 Comments   
Comment by Chuong Doan Huy [ 12/Jul/18 ]

Hi Gourav, trung.luu

I have investigated this and found that our current test connection function only check the connection to the server with proper clientId, clientPassword, agentName, url.

We will improved the function to verify the connection to the specific project, source language, target language...

Comment by Chuong Doan Huy [ 16/Jul/18 ]

Hi Gourav, trung.luu

I have applied a fix by checking more for projectCode, fileFormat (beside url, clientId, clientPassword, agentName).

For source language and target languages, unfortunately we can not check connection. This is because check connection function can work with empty batch which does not have target languages chosen, so we can not compare it with these languages configured in the PD

Generated at Mon Feb 12 00:29:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.