Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WarFileTest.checkEbextensionsValidityThrowsExceptionNoDir broken. #19

Open
nhekfqn opened this issue Feb 10, 2015 · 24 comments
Open

WarFileTest.checkEbextensionsValidityThrowsExceptionNoDir broken. #19

nhekfqn opened this issue Feb 10, 2015 · 24 comments

Comments

@nhekfqn
Copy link
Contributor

nhekfqn commented Feb 10, 2015

That test does not actually check that exception is thrown. If no exception is thrown, assert will not be called and test will pass.

@Test
    public void checkEbextensionsValidityThrowsExceptionNoDir()
        throws IOException {
        final ZipFile zip = Mockito.mock(ZipFile.class);
        Mockito.when(zip.getEntry(".ebextensions")).thenReturn(null);
        final WarFile war = new WarFile(zip);
        try {
            war.checkEbextensionsValidity();
        } catch (final MojoFailureException exception) {
            MatcherAssert.assertThat(
                exception.getMessage(),
                Matchers.equalTo(
                    ".ebextensions directory does not exist in the WAR file"
                )
            );
        }
@yegor256 yegor256 added the bug label Feb 13, 2015
@dmarkov
Copy link

dmarkov commented Feb 16, 2015

I am aware of the task, give me some time to find a developer...

@dmarkov
Copy link

dmarkov commented Feb 16, 2015

@nhekfqn many thanks, 15 mins added to your acc for reporting this bug, pmt ID 51683468

@nhekfqn
Copy link
Contributor Author

nhekfqn commented Feb 16, 2015

@dmarkov Can I ask to assign this to me?

@dmarkov
Copy link

dmarkov commented Feb 23, 2015

@apocarteres the issue is yours, please help

@dmarkov
Copy link

dmarkov commented Oct 2, 2015

@tmjee the task is for you now, follow these guidelines. Don't hesitate to ask any technical questions right here... This task's budget is 30 mins. This is exactly how much will be paid when the problem explained above is solved. See this for more information

@dmarkov dmarkov added the @tmjee label Oct 2, 2015
@tmjee tmjee mentioned this issue Oct 3, 2015
@tmjee
Copy link

tmjee commented Oct 3, 2015

@dmarkov fixed in pull request #29

@tmjee
Copy link

tmjee commented Oct 6, 2015

@nhekfqn Merged. Pls close this issue. Thx

@dmarkov
Copy link

dmarkov commented Oct 6, 2015

@dmarkov fixed in pull request #29

@tmjee OK thanks

@dmarkov dmarkov removed the @tmjee label Oct 13, 2015
@dmarkov
Copy link

dmarkov commented Aug 5, 2016

@prondzyn it's your task, go ahead

@prondzyn
Copy link
Contributor

prondzyn commented Aug 5, 2016

@dmarkov I reviewed history of this task, PR, and source code and this issue is already fixed adding extra checking.

Please see line: https://github.com/jcabi/jcabi-beanstalk-maven-plugin/blob/master/src/test/java/com/jcabi/beanstalk/maven/plugin/GenericMojoTest.java#L178

In meanwhile the problematic test was renamed and moved to GenericMojoTest class.

I will ask task author to close this ticket.

@prondzyn
Copy link
Contributor

prondzyn commented Aug 5, 2016

@nhekfqn please close the issue. It was already fixed in PR #29.

@prondzyn
Copy link
Contributor

prondzyn commented Aug 8, 2016

@nhekfqn ping

@prondzyn
Copy link
Contributor

@dmarkov looks like author of this task is no longer active on GitHub - zero commits through last year. But the issue is fixed as I mentioned before. Can you close the task or do something about it?

@prondzyn
Copy link
Contributor

@nhekfqn I'm asking once again, please close the issue. It was already fixed in PR #29.

@prondzyn
Copy link
Contributor

@dmarkov still does not respond. What should I do with this task?

@dmarkov
Copy link

dmarkov commented Aug 12, 2016

@dmarkov looks like author of this task is no longer active on GitHub - zero commits through last year. But the issue is fixed as I mentioned before. Can you close the task or do something about it?

@prondzyn sure

@prondzyn
Copy link
Contributor

@dmarkov can you close the task?

@dmarkov
Copy link

dmarkov commented Aug 22, 2016

@prondzyn this task is in your hands for 16 days already

added -30 to your rating, now it is equal to +60

@prondzyn
Copy link
Contributor

@dmarkov why? I was asking you 10 days ago about closing this task:

@dmarkov looks like author of this task is no longer active on GitHub - zero commits through last year. But the issue is fixed as I mentioned before. Can you close the task or do something about it?

@prondzyn sure

@prondzyn
Copy link
Contributor

@dmarkov please close the task

@dmarkov
Copy link

dmarkov commented Aug 25, 2016

@dmarkov please close the task

@prondzyn thanks

@dmarkov
Copy link

dmarkov commented Aug 25, 2016

@prondzyn the task is overdue, and I have to re-assign it to someone else. Please, stop working with it immediately. In general, we're against overdue tasks, check this page... -60 to your rating, your total score is -30

@prondzyn
Copy link
Contributor

@dmarkov this stinks. @yegor256 I know that you will say same as @dmarkov but please review history of this task and my comments. I reviewed it and contacted with an author but he is no longer active. I know the "no obligations" and other rules but there are some lack with them in some cases. Think about it.

@dmarkov
Copy link

dmarkov commented Sep 5, 2016

@dmarkov this stinks. @yegor256 I know that you will say same as @dmarkov but please review history of this task and my comments. I reviewed it and contacted with an author but he is no longer active. I know the "no obligations" and other rules but there are some lack with them in some cases. Think about it.

@prondzyn @yegor256 could you please help us here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants