Skip to content

Fixed indexing of warnings for documentation reporter #373

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

Merged
merged 7 commits into from
Jul 2, 2017

Conversation

Pazus
Copy link
Member

@Pazus Pazus commented Jun 27, 2017

address #350

@Pazus Pazus added the bugfix label Jun 27, 2017
@Pazus Pazus added this to the v3.0.2 milestone Jun 27, 2017
@Pazus Pazus self-assigned this Jun 27, 2017
@@ -151,7 +153,8 @@ create or replace type body ut_documentation_reporter is

if a_item.warnings is not null and a_item.warnings.count > 0 then
for i in 1 .. a_item.warnings.count loop
self.print_text(' ' || i || ') ' || a_item.path);
l_warning_index := l_warning_index + 1;
self.print_text(' ' || l_warning_index || ') ' || a_item.path);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you make both error_no and warning_no uniformly indented

lpad(l_warning_index,5)

I don't expect any report to have more than 9999 errors or warnings in it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. It is already done for errors, so I made it only for warnings

@coveralls
Copy link

coveralls commented Jun 27, 2017

Coverage Status

Coverage increased (+0.007%) to 91.714% when pulling 7b5e02e on Pazus:issue-350 into 65d0169 on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jun 29, 2017

Coverage Status

Coverage increased (+0.2%) to 91.868% when pulling 6efe324 on Pazus:issue-350 into 021eead on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 1, 2017

Coverage Status

Coverage increased (+0.2%) to 91.868% when pulling 6fcff0e on Pazus:issue-350 into 021eead on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 1, 2017

Coverage Status

Coverage increased (+0.2%) to 91.868% when pulling 534545d on Pazus:issue-350 into 021eead on utPLSQL:develop.

@jgebal jgebal merged commit ea2573e into utPLSQL:develop Jul 2, 2017
@jgebal jgebal removed the in progress label Jul 2, 2017
Pazus added a commit that referenced this pull request Jul 18, 2017
### Documentation
  #399 Documentation now refers to [migration](https://github.com/utPLSQL/utPLSQL-v2-v3-migration) project
  #386 Documentation now refers to a valid object name: `ut_file_mapping`
  #362 Install and Uninstall scripts are now much more readable
  #361 Install guide now provides snippet on how to download latest release on Windows

### Installation
  #396 Added override user/password/tablespace for install_headless
  #384 Installation is now smooth even if profiler tables already exist

### Internal improvements
  #388 Improved reporting from RunTest
  #363 Fixed publishing of release documentation history

### Improvements and fixes
  #407 Fixed rare issue with `ORA-22813: operand value exceeds system limits`
  #403 Stack trace is now properly parsed on all machines
  #397 The `--%disabled` annotation on suite level is now reporting all tests as disabled
  #395 Coverage reporting is now properly filtering test packages on that use suitepath
  #390 Line of code for failed expectation is now also shown for unit tests owned by other users
  #380 Line no of failed test is now properly reported when using `ut.fail`
  #375 Annotation parameter list can now have spaces before/after brackets
  #373 Warnings in documentation reporter are now properly numbered
  #372 Documentation reporter is now providing a timing information for each test
  #370 by xUnit reporter now displays name of the package/procedure if suite/test has no description
  #369 Fixed errors with multi-byte characters in conversion from/to clob
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants