René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Use of fullstop character in  --%context(\u003cname\u003e)","articleBody":"### Describe the bug\r\nUsing a full stop character in ```--%context(\u003cname\u003e) ```  will cause all other contexts in the suite to be executed under an entirely different suite as seen in the output section below. The reason for this I believe is because the way a context name is interpreted as a path to allow users to execute specific contexts. \r\n\r\n### Version Info\r\n**utPLSQL:**  v3.1.6.2735\r\n**SQL Developer:**  19.1.0.094\r\n\r\n### To Reproduce\r\n**1. Create tests**\r\n```sql\r\ncreate or replace package test_context_bug_1 is\r\n\r\n  --%suite\r\n\r\n  --%context(suite_1 context_1)\r\n\r\n    --%test\r\n    procedure test1;\r\n\r\n  --%endcontext\r\n  \r\n  --%context(suite_1 context_2)\r\n\r\n    --%test\r\n    procedure test2;\r\n\r\n  --%endcontext\r\n\r\nend;\r\n/\r\n\r\ncreate or replace package body test_context_bug_1 is\r\n\r\n  procedure test1 is\r\n  begin\r\n    ut.expect( 1 ).to_equal( 1 );\r\n  end;\r\n\r\n  procedure test2 is\r\n  begin\r\n    ut.expect( 1 ).to_equal( 1 );\r\n  end;\r\n\r\nend;\r\n/\r\n\r\ncreate or replace package test_context_bug_2 is\r\n\r\n  --%suite\r\n  \r\n  --%context(suite_2 context_1)\r\n  \r\n    --%test\r\n    procedure test1;\r\n\r\n  --%endcontext\r\n  \r\n  --%context(suite_2 context_2)\r\n\r\n    --%test\r\n    procedure test2;\r\n\r\n  --%endcontext\r\n\r\nend;\r\n/\r\n\r\ncreate or replace package body test_context_bug_2 is\r\n\r\n  procedure test1 is\r\n  begin\r\n    ut.expect( 1 ).to_equal( 1 );\r\n  end;\r\n\r\n  procedure test2 is\r\n  begin\r\n    ut.expect( 1 ).to_equal( 1 );\r\n  end;\r\n\r\nend;\r\n/\r\n ```\r\n**2. Add a full stop in a context name**\r\n``` sql \r\n--%context(suite_2. context_2)  \r\n```\r\n\r\n**3. Run tests**\r\n``` sql\r\nSET SERVEROUTPUT ON SIZE UNLIMITED\r\nEXECUTE ut.run(); \r\n```\r\n\r\n\r\n### Outputs\r\n**Expected output:**\r\n```\r\ntest_context_bug_1\r\n  suite_1 context_2\r\n    test2 [.003 sec]\r\n  suite_1 context_1\r\n    test1 [.002 sec]\r\n \r\ntest_context_bug_2\r\n  suite_2 context_2\r\n    test2 [.002 sec]\r\n  suite_2 context_1\r\n    test1 [.002 sec]\r\n \r\nFinished in .013272 seconds\r\n4 tests, 0 failed, 0 errored, 0 disabled, 0 warning(s)\r\nPL/SQL procedure successfully completed.\r\n```\r\n\r\n**Actual output:**\r\n```\r\ntest_context_bug_1\r\n  suite_2 context_1\r\n    test1 [.003 sec]\r\n  suite_1 context_2\r\n    test2 [.001 sec]\r\n  suite_1 context_1\r\n    test1 [.001 sec]\r\n \r\ntest_context_bug_2\r\n  suite_2. context_2\r\n    test2 [.003 sec]\r\n \r\nFinished in .01466 seconds\r\n4 tests, 0 failed, 0 errored, 0 disabled, 0 warning(s)\r\nPL/SQL procedure successfully completed.\r\n```\r\n\r\n### Expected behavior\r\nWhen a full stop is present in ```--%context(\u003cname\u003e) ```  the other contexts in the suite shouldn't be executed under another suite.\r\n","author":{"url":"https://github.com/BrianGubbins","@type":"Person","name":"BrianGubbins"},"datePublished":"2019-07-02T17:39:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/966/utPLSQL/issues/966"}