Tech Nuggets and Thoughts Nikhil Wanpal

In the eighth episode, we discuss coderetreat covering:


What is Coderetreat
What is GDCR
The success of GDCR event in Pune
The spiritual aspects of Coderetreat! ( ;-) )
How to run your own Coderetreat
Codereteat is not a hackathon!
Letting go! (of your code)
Our favorite constraints
What we learnt from the event
Why should you have a Coderetreat?

In this episode we discuss these aspects of unit testing:


jUnit, TestNG feature overview
Mocha and Chai: bdd and tdd styles
Cobertura and Istanbul, nyc
Cucumber, Feature Files and verbosity
Introducing Cucumber to teams
Spock
End-to-end testing / integration testing tools: Selenium, Appium
End-to-end API testing: Postman
Contract Tests: Pact, Spring Cloud Contract
Smoke Tests, testing in production and reverting on failure.
Mocking Tools: JMockit, Mockito and PowerMock, Wiremock
Your acceptance tests are next layers integration tests.

In this episode we discuss these aspects of unit testing:


Test FIRST: Repeat-ability
Fiasco in testing time based code: time zones, time adjustments, leap years, day light saving
Calendar trivia
Testing multi-threaded code
Parallel tests, and test isolation
DRY and Wet
Assertions in unit tests and coverage
Mutation testing
Should we trust coverage? How much coverage is enough?
Peer Confidence
To mock or not to mock, that is the question!

In this episode we discuss the aspects of unit testing:


Types of changes in code: structural and behavioural
Fast tests make you fast
Learning Tests
Broken console.log
Single asserts in tests
Tests and code handover.
Why trust tests?
Slow tests, leaving process boundaries and unpredictability in tests.
What are: test doubles, mocks, dummies, stubs, spies and fakes?
To mock or not to mock.

We talk about software testing touching points as:
1. What is testing?
2. What are software requirements?
3. The test pyramid
4. Importance of business in software and what it means for testing.
5. Test principles: F.I.R.S.T
6. Test First principle
7. What is a unit, in unit testing?

Circular Depedency is cyclic depedency between classes, packages, modules or services. It adversely affects software's health and productivity of developers.
Here we discuss how to identify, avoid and solve circular dependency in software. We discuss how it arises at all levels of abstraction in software, whether it is good or bad, tools we can use to identify and eliminate the depdency.