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

Jason Gerlowski edited comment on SOLR-12137 at 5/1/23 3:31 PM:
----------------------------------------------------------------

It's probably not realistic.  And of course this ticket should be rewritten to 
reference BATS instead of bin-test.

But IMO the general idea of testing for our Windows batch scripts is still A 
Good Thing, even if we can't see a path right now that'd get us there.  Is 
there a cost to keeping it open?


was (Author: gerlowskija):
It's probably not realistic  And of course this ticket should be rewritten to 
reference BATS instead of bin-test.

But IMO the general idea of testing for our Windows batch scripts is still A 
Good Thing, even if we can't see a path right now that'd get us there.  Is 
there a cost to keeping it open?

> Create Windows-equivalent of bin-test/test
> ------------------------------------------
>
>                 Key: SOLR-12137
>                 URL: https://issues.apache.org/jira/browse/SOLR-12137
>             Project: Solr
>          Issue Type: Sub-task
>          Components: scripts and tools
>    Affects Versions: 8.0
>            Reporter: Jason Gerlowski
>            Priority: Minor
>
> SOLR-11749 introduced a regression suite for the {{bin/solr}} scripts.  
> Currently this suite (located in {{solr/bin-test}} only covers the *nix copy 
> of {{bin/solr}}.  No tests are run for the Windows version.
> This JIRA involves porting the existing {{bin-test/test}} logic (along with 
> the accompanying tests) to Windows batch.  This will allow both versions of 
> the script to be tested, and will open the door to future steps, like hooking 
> the suite into one of ant's test targets.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to