Course code: PASA-3
  • Years with company: 2
  • Years programming: 12
  • Primary programming language: C
  • Other programming languages: C++
  • Unit test harnesses: Mock Client/Server for input and verify logs/prints for output
  • Something else: My area of expertise is wireless network communication protocols like Bluetooth and WiFi. Most of time I'm involved in developing middleware software on these communication protocols.
  • Test practice now: Most of the time I mock input from client/server to middleware and verify the output in logs/prints. Since there is a third-party dependency on lower layers, most of the times it is difficult to mock the device behavior.
  • Target system: Automotive embeded systems
  • Dev tools: QNX IDE, Enterpeise Architect, UML
  • Build time: 5-30 minutes
  • Coding standard: PASA coding standard, C99
  • Function too long: multiple actions/logical blocks, number of lines
  • Code reviews: PASA code review guidelines using collaborator
  • Code time: 40%
  • Test time: 40%
  • Debug time: 20%
  • Favorite thing about dev: Using the tools, methods and best practices to create or enhance re-usable software modules within the estimated time.
  • Least favorite thing about dev: Writing a piece of code never gets executed. Writing throwaway codes.
  • Tdd knowledge: TDD helps in visualize the use-case and write test cases first. Helps write only necessary code. Spend less time in debugging and reduce the integration testing time.
  • Why are you attending: I would like to understand how to mock asynchronous events from lower layers and application layers to simulate different timing conditions observed in the field testing.
  • Back