In case you use Azure AD or other SSO clients in your tests, you might have used and kept the test user credentials in the code. This is of course not ideal and it is preferred to keep the secrets out of the repository before the senior gets to review it and lose it.
Hello reader, in case you clicked on this article, it probably means that you would like to get an interview at Google once or already have it planned and you are just gathering some info as I did. I obviously cannot expose the coding challenges even though I would love to see how you would solve them and what you think about them. However, I would like to share my experience that might help you land an interview and also not fail it as I did.
The best practice to configure an Angular app is to define multiple environment files and use one of them at compilation time. Unfortunately, with line-of-business apps, I mostly saw that the usual way is to build a single bundle which is then deployed through individual stages, and each starts it with a different configuration file...
Angular CLI projects come with a testing framework and automatically generated test files, however, it is still quite a lot of work to set up those tests for services or components which requires multiple dependencies. In this article, I am going to show you a trick on how to take advantage of already existing module configuration and avoid setting up your (test)bed all the time!
Have you ever wondered how to bind an enum value or a constant in a template of an Angular component? Don't repeat yourself there and take advantage of pipes!