[ 
https://issues.apache.org/jira/browse/CB-14211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16604386#comment-16604386
 ] 

ASF GitHub Bot commented on CB-14211:
-------------------------------------

raphinesse edited a comment on issue #627: CB-14211: Run test suite in 
PowerShell and cmd.exe
URL: https://github.com/apache/cordova-lib/pull/627#issuecomment-418725174
 
 
   @janpio @oliversalzburg This all started with #622 which challenges the 
correctness of the escaping done in lib for some shells. Thus, we should start 
with unit tests for `superspawn` in `cordova-common` that test (or show the 
absence of) escaping. For example by calling `superspawn` to write some special 
characters to a file and check the result.
   
   After we have a better understanding of the problems at hand and we still 
feel it's necessary, we could select a few tests to form a smoke test suite for 
lib on PowerShell that we run on CI in addition to our regular tests. What do 
you think?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Run Windows/AppVeyor test suite in both PowerShell and Command Prompt
> ---------------------------------------------------------------------
>
>                 Key: CB-14211
>                 URL: https://issues.apache.org/jira/browse/CB-14211
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: cordova-lib
>            Reporter: Oliver Salzburg
>            Priority: Major
>
> I thought it could be useful to run the test suite in both shells, just to be 
> safe.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to