@Reload(MyClass.class) annotation

[levBagryansky]

In order to initialize static fields of class for test we can implement such annotation. I should reinitialize static fields of class before test starting. The problem is which value to init them.

[github-actions]

@levBagryansky thanks for the report, here is a feedback:

Problems

• Clear Title: The report lacks a succinct and descriptive headline that outlines the problem.
• Steps to Reproduce: The bug report fails to include any instructions or methods to recreate the issue.
• Expected vs. Actual Results: The report does not detail the expected outcome versus the actual outcome.

Suggestions

• Clear Title: Start with a clear, concise title that quickly summarizes the issue. The title should give an idea of what the bug is about. For example, "Issue with @reload(MyClass.class) annotation: Unclear initialization of static fields before testing".
• Steps to Reproduce: Provide a detailed, step-by-step procedure to reproduce the issue. This will be very helpful for those working on the fix. Mention the exact sequence of actions that lead to the bug. If applicable, include the input data used.
• Expected vs. Actual Results: Clearly specify what the expected result or behavior should be, and contrast this with what is currently happening. This gives a clear understanding of why the current situation is a problem.
• Additional Information: If possible, provide any additional information that may be helpful, like screenshots, error messages, logs, or the environment in which the bug was encountered. This additional context could be very useful for those trying to understand and fix the issue.
• Language and Clarity: Ensure that the description of the issue is clear, concise, and free of jargon or colloquial language. The bug report should be understandable to anyone reading it, not just those familiar with the project.
• Formatting: Proper formatting can greatly increase the readability of the bug report. Break up large blocks of text into smaller paragraphs, use bullet points or numbered lists where appropriate, and use bold or italics for emphasis when necessary.
• Remember, a well-formulated bug report can save a lot of time and effort in the bug fixing process.

Please fix the bug report in order it to get resolved faster.
Analyzed with gpt-4

[levBagryansky]

@volodya-lombrozo WDYT

[volodya-lombrozo]

@levBagryansky I don't think we need it. Explained it here