GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — Use of fullstop character in --%context(<name>) · Issue #966 · utPLSQL/utPLSQL Closed Labels DescriptionDescribe the bugUsing a full stop character in Version InfoutPLSQL: v3.1.6.2735 To Reproduce1. Create tests create or replace package test_context_bug_1 is --%suite --%context(suite_1 context_1) --%test procedure test1; --%endcontext --%context(suite_1 context_2) --%test procedure test2; --%endcontext end; / create or replace package body test_context_bug_1 is procedure test1 is begin ut.expect( 1 ).to_equal( 1 ); end; procedure test2 is begin ut.expect( 1 ).to_equal( 1 ); end; end; / create or replace package test_context_bug_2 is --%suite --%context(suite_2 context_1) --%test procedure test1; --%endcontext --%context(suite_2 context_2) --%test procedure test2; --%endcontext end; / create or replace package body test_context_bug_2 is procedure test1 is begin ut.expect( 1 ).to_equal( 1 ); end; procedure test2 is begin ut.expect( 1 ).to_equal( 1 ); end; end; / 2. Add a full stop in a context name --%context(suite_2. context_2) 3. Run tests SET SERVEROUTPUT ON SIZE UNLIMITED EXECUTE ut.run(); OutputsExpected output: Actual output: Expected behaviorWhen a full stop is present in ActivityMetadataMetadataAssigneesLabelsTypeProjectsMilestoneRelationshipsDevelopmentIssue actions |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |