Skip to content

Qprofiler qio #235

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 10 commits into from
Feb 3, 2021
Merged

Qprofiler qio #235

merged 10 commits into from
Feb 3, 2021

Conversation

ChristinaXu2017
Copy link
Contributor

@ChristinaXu2017 ChristinaXu2017 commented Feb 1, 2021

Description

  • The org.qcmg.ma, org.qcmg.fast and org.qcmg.gff are deleted from qio, the alternative new pacake is org.qcmg.qio.ma, org.qcmg.qio.fasta and org.qcmg.qio.gff. these new package is based on org.qcmg.qio.record.RecordReader (refer to pull request create universal reader and writer #209).
  • update qprofiler by using new qio packages.
  • update qbamannotate by using new qio::ma package
  • use org.junit.Assert to replace the deprecated junit.framework.Assert inside unit tests
  • add unit test method to delete output qprofiler.xml after each test run.
  • tidy up code.

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

the unit test is created and updated, regression test in our TC box was created.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

return mismatchCount;
}

// public MAMappingParameters getParameters() {
Copy link
Contributor

Choose a reason for hiding this comment

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

delete

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

@@ -39,6 +40,17 @@ public void setup() throws IOException {

createTestFile(DODGY_GFF_FILE_NAME_FILE, getDodgyFileContents());
}

@After
public void tidyUp() throws IOException {
Copy link
Contributor

Choose a reason for hiding this comment

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

It's generally safer to use the TemporaryFolder class to setup files in each test method, as that way, junit takes care of removing the files once they have been used. I know that in this case the original code is not yours - do you know which test method is producing the qprofiler.xml file? If so, perhaps that method(s) can be updated to take a temp file as the output?

Copy link
Contributor Author

@ChristinaXu2017 ChristinaXu2017 Feb 3, 2021

Choose a reason for hiding this comment

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

qprofiler.xml is a default output if the "--output" option is not called.
I think it is a good idea, but I agree it should not be always tested. The unit test is updated, hence we test the qprofiler with "--output" option, unless the unit testing the default output.

This problem should be solved

Copy link
Contributor

@holmeso holmeso left a comment

Choose a reason for hiding this comment

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

thanks for the changes

@ChristinaXu2017 ChristinaXu2017 merged commit 603fa1f into master Feb 3, 2021
@ChristinaXu2017 ChristinaXu2017 deleted the qprofiler_qio branch February 12, 2021 03:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants