Reordered columns in describe_pipeline to make main objective first column

[angela97lin]

No description provided.

[codecov]

Codecov Report

Merging #94 into master will increase coverage by 0.13%.
The diff coverage is 96.77%.

@@            Coverage Diff             @@
##           master      #94      +/-   ##
==========================================
+ Coverage   92.41%   92.54%   +0.13%     
==========================================
  Files          47       47              
  Lines        1226     1248      +22     
==========================================
+ Hits         1133     1155      +22     
  Misses         93       93

Impacted Files	Coverage Δ
evalml/pipelines/pipeline_base.py	96.66% <100%> (+0.05%)	⬆️
evalml/objectives/utils.py	100% <100%> (ø)	⬆️
evalml/tests/test_autoclassifier.py	100% <100%> (ø)	⬆️
evalml/models/auto_base.py	91.5% <90.9%> (+0.26%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d7bd82b...9cb6ae5. Read the comment docs.

[rwedge]

Could you add a test case?

[angela97lin]

Sure! Where's a good place to test this? (I wasn't able to find any previous tests for describe_pipeline?)

[rwedge]

test_additional_objectives in test_autoclassifier.py is fairly similar

[angela97lin]

Hmmm, since we only change the order of what's logged/printed and not what is actually stored in the dictionary (pipeline_results["all_objective_scores"]), it's difficult to check the returned dictionary...

[rwedge]

pytest has fixtures (capsys and caplog) you can use to examine the output of a test case

[kmax12]

fixes #86

[angela97lin]

Also fixes #101 and #102

[rwedge]

Looks good