Devlopment tales

Change-Based Testing in a Yarn-managed monorepo Change-Based Testing in a Yarn-Based Monorepo In the world of software development, especially when working with large projects, efficiency is key. One approach to manage large codebases effectively is by using a monorepo, where multiple projects are stored in a single repository. Yarn, a popular package manager for JavaScript, provides powerful tools to manage such monorepos. One of the standout features is the ability to run commands across multiple workspaces with precision and efficiency. In this blog post, we'll explore how to leverage Yarn's capabilities for change-based testing, focusing on a specific command: yarn workspaces foreach --since --recursive --topological --exclude root -vv exec eslint src . Understanding the Command Before diving into the details, let's break down what this command does: yarn workspaces foreach : This is the base command to run a specified operation...

Hi All, To share my knowledge and experience in testing AngularJS apps, I am presenting on using Protractor for end-to-end testing of AngularJS applications at the Wellington AngularJS meetup. If you are planning or already using AngularJS for your front-end development and interested to know some best practices for the end to end testing of web apps, do RSVP to this event . Cheers!!

Xcode 7 has introduced new UI testing features fully integrated into the IDE. I learned about the new APIs and how UI testing fits in with existing testing features in Xcode. Also got to see how to get started by recording your app, and how to efficiently craft and maintain UI tests. check this link introducing this API and UI testing tool in WWDC/2015 Though this tool is in beta stage, IT industry has taken this as a tool for future UI testing for apple apps and have started using it already. I came across another good article related to this. It summarizes the WWDC 2015 UI Testing talk and gives the detail of coming beta releases as well. Check it out here

The development of Angular 2 is on its way with much talk, hype, and fanfare. Surprisingly, there is not much being said about unit testing. As a responsible developer, you have undoubtedly already written a giant unit test suite to achieve ‘near perfect’ code coverage, and I'm here to let you know, there is no need to throw that all away! While Angular 2 is currently in ‘developer preview’, implying that nothing serious should be built with it currently, the Angular Team has already created a giant wealth of unit tests and a custom testing setup: (https://github.com/angular/angular/tree/master/modules/angular2/test). Unfortunately, it is not easy to set this up for yourself. So this post should help you get started. link to full post here

Firstly, what are Page Objects? Here is a definition from the Selenium team: Page Object is a Design Pattern which has become popular in test automation for enhancing test maintenance and reducing code duplication. A page object is an object-oriented class that serves as an interface to a page of your AUT. The tests then use the methods of this page object class whenever they need to interact with that page of the UI. The benefit is that if the UI changes for the page, the tests themselves don’t need to change, only the code within the page object needs to change. Subsequently all changes to support that new UI are located in one place. Using Page objects in test cases has been very useful. It will feel hard and time consuming initially but, once you have all page objects up and running. Its going be a smooth ride . Till now writing test cases for an Angular Apps has been smooth ride. Thanks to some good articles online to get me going. I have found some very helpful resour...