HOMEWORK 1 REFACTORING AND LEGACY CODE

HOMEWORK 1 REFACTORING AND LEGACY CODE

Even though I could have knocked out the homework in probably less than half the time without testing, I really liked the practice. So all I have to do now is concentrate on writing whatever little bit I’m working on now, instead of trying to keep the entire app in my head and worry about not breaking anything else. Then at the very end I wrote the cucumber integration tests for the sad paths. Our feature in a nutshell: Then I wrote the unit test for the controller. I am still very new to Rspec and TestUnit syntax, and spend so long trying to figure out exactly how to phrase things.

So instead of putting all the tests there, I just wrote a few to make sure the controller was asking the model for that information. Only administrators can merge articles. Our feature in a nutshell: Even though I could have knocked out the homework in probably less than half the time without testing, I really liked the practice. So even though at first they had no idea how to teach this, they set out to do so in this class. Last week we were asked to fix a bug in it.

But this time I played around with them in the debugger gem. This week’s SaaS homework has been the most elaborate so far. So instead of putting all the tests there, I just wrote a few to make sure the controller was asking the model for that information.

SaaS Legacy Homework 2: Lessons Learned · jlc

Only administrators can merge articles. So even though at first they had no idea how to teach this, they set out to do so in this class. I spent a LONG time on this homework.

homework 1 refactoring and legacy code

You can find out more here. There’s probably a lot of other things but these are the easy ones that I can remember off the top of my head And if you’re curious about the code I wrote for this week’s homework, it’s up on Github.

  CONTOH ESSAY KGSP

homework 1 refactoring and legacy code

Related Posts Week 4: So all I have to do now is concentrate on writing whatever little bit I’m working on now, instead of trying to keep the entire app in my head and worry about not breaking anything else.

As the instructors explain in the lectures, after teaching the class for a while, they asked some of the top software companies what one thing they wish graduates of computer science programs would learn before entering the workforce.

The title and author will be from one of the two articles. Then at the very end I wrote the cucumber integration tests for the sad paths.

The hardest part was writing the tests. First I wrote the Cucumber integration tests for the happy path only. And thus we have legacy homework 1 and 2 last week and this week. But I’m proud to say that I stuck to it this time and wrote all the tests before writing the actual code except for the view and some skeleton methods so it didn’t throw method-not-found errors–basically I had to get it to the point where the tests failed for the right reasons and not because it couldn’t find some method.

If what I’m doing now will break something else, then I’ll know about it soon enough if I wrote my tests right.

And the comments of all previous articles if any will now be comments of this article. This week, we had to add a new feature! I also feel like testing frees up my brain from worrying about every little bit of my application. I’ve used them in previous apps but they always seemed hmoework a mystery to me. Last week we were asked to fix a bug in it.

  NORDSTROM CASE STUDY SPH

That shouldn’t be a surprise because writing the test is always the hardest part for me! Instead of working on a new custom app, we are given an existing app the Typo blog platform that has a long history, sometimes messy code, and spotty test coverage. It was hard but satisfying.

The one thing that was SUPER helpful was using the debugger refactorkng and plain old rails console with the –sandbox option while writing the tests, because it helped me figure out exactly how refactoding get to certain elements in order to test them.

Then I wrote the unit test for the controller.

SaaS Legacy Homework 2: I really like the idea of my git legacu telling the story of my code. At last I allowed myself to write some actual code, which didn’t take long.

SaaS Legacy Homework 2: Lessons Learned

Then I had to write a bunch of unit tests for the model. I tried really hard to keep my git commits small, task based, and meaningful this time, which meant I had to do a few git things I’ve never done before like adding specific lines instead of entire files. Our feature in a nutshell: I am still very new to Rspec and TestUnit syntax, and spend so long trying to figure out exactly how to phrase things.

Twitter Fitter—the tweet generator! The body of the new article will be a concatenation of the two previous articles.