![]() These types of tests should be suffixed withĬheck instead. In the /test directory should not be named with Test as the suffix, as this will cause them to execute in someĮnvironments without a GraphProvider being initialized by a suite. Tests that are designed to use a GraphProvider implementation in conjunction with AbstractGremlinTest and are Failing to do this cleanupĬan cause problems for some graph providers. Instance is constructed within the test manually, that it be closed on exit of that test. If writing tests in one of the test suites, like gremlin-test, it is important to remember that if a new Graph TestHelper will properly create file system structure in the appropriate buildĭirectory thus allowing proper clean-up between test runs. If it is necessary to create files on the filesystem, do not hardcode directories - instead, use the TestHelper toĬreate directory structures. ![]() This resolution, it should be easy to come back to them later when needed.Īvoid use of println in tests and prefer use of a SLF4j Logger instance so that outputs can be controlled in a Item is a good idea but likely will not be implemented in any foreseeable future. Resolution has special meaning and care should be taken with this particular option: "Later". In most cases, this will mean "Fixed" for a "Bug" or "Done" for an "Improvement". The "resolution" field which is set on the close of the issue should specify the status most closely related to why Tasks that are "easy" for a potential new contributor to jump into and do not have significant impact to urgently The "trivial" option should be reserved for The "priority" field can be arbitrarily applied with one exception. This is a field usually only set by committers. Which that particular issue will completed. The "affects/fix version(s)" fields should be appropriately set, where the "fix version" implies the version on The "deprecation" label which is assigned to an issue that includes changes to deprecate a portion of the API. This label is important when organizing release notes. The "breaking" label which marks an issue as one that is representative of a change in the API that mightĪffect users or providers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |