Apache Maven

3rd Day of 100 Days of CodeDay 3 of my 100 Days of coding and I have my commit done. Now I can peek at something else. I was looking into using PostGres as the database under a Node app using TypeScript
 as a follow up to today’s work on building a RESTful API With Node and TypeScript for superheros.
Like for instance, I saw a job opening for a UX UI Web Developer. Ok, is this a UX person, a UI design person, or a full-on developer?

  • HTML5, CSS3, JavaScript & jQuery [check]
  • Scrum, Extreme Programming, and/or other Agile methodologies (ok, how we work, not what we do)[check]
  • Angular JS & Angular 2(Thank heavens today’s work was working with TypeScript)[check]
  • AJAX with JSON and XML (now I’m getting a Alert flag) As I have found that recent coders are calling it a REStFull API, with JSON. AJAX and XML reads Java-shop to me.
  • Experience with a Maven build environment(This confirms it, Java-shop!)

Ok shoot, I’m game. UX UI Web Developer


Well then, time to go back to CVS, Subversion, Apache ANT scripts and Maven builds. Let’s go back to the Future, or a Blast from the Past! I like reading the simple version of most things, and Tutorials Point is usually on point. This post seemed good as well.

Testing is Good

Testing is Good. Pyramids are Bad. Ice Cream Cones are the Worst

Monday’s Fullstack meeting at Manheimfists of reason speaker was about Testing mindsets. All across the board. Stephen Fishman, Sr Director, Application Architecture spoke passionately about WHY Testing is Good. Pyramids are Bad. Ice Cream Cones are the Worst

Many engineering and QA professionals are familiar with and lean on the Testing Pyramid made popular by Martin Fowler. Too bad it doesn’t work for in-transformation teams and doesn’t offer hope to teams looking to create change in an organizations’ commitment to drive towards “continuous testing” (especially when everyone wants to fight about tracking coverage levels). This talk will focus on showing what has gone wrong with the testing pyramid and what new model might work better for in-transformation teams.

Specific items this talk will cover:

– What is continuous testing and why is it necessary for a CICD transformation

– What is the testing pyramid and what are its strengths

– What is the testing ice-cream cone and why is it generally bad

– Where does the pyramid model fall short for in-transformation/enterprise teams

– What is a new model that could work better for in-transformation/enterprise teams

Here are some sample articles Stephen wrote on the topic:

https://medium.com/@fistsOfReason/testing-is-good-pyramids-are-bad-ice-cream-cones-are-the-worst-ad94b9b2f05f#.6qsvqv7ce

http://www.cmswire.com/analytics/when-it-comes-to-metrics-size-matters/

 
Remember Testing is Good. Kind of like those maze movies where they program and brainwash the kids to believe WICKED is good. However in this case Testing is Good, you just have to know how to apply your creative energies and in what doses to where.

JUnit Testing

JUnit has matured to become the most important tool when it comes to automated developer tests in Java. Supported by all IDEs and build systems, it empowers programmers to deliver software features reliably and efficiently. However, writing good unit tests is a skill that needs to be learned; otherwise it’s all too easy to end up in gridlocked development due to messed up production and testing code. Acquiring the best practices for unit testing will help you to prevent such problems and lead your projects to success with respect to quality and costs.

Some skills in this stack are;

  • Using advanced JUnit 4 features
  • Improving code coverage, (width and depth)
  • Automating JUnit tests stacks and scripts
  • Monitoring code quality with reports
  • Writing JUnit tests for the database and web tiers
  • Refactor legacy(older) code
  • Mock external dependencies using Mockito
  • Writing testable code using test-driven development mindset