Like the summer breeze

One thing that fascinates me about Lana del Rey is her love for the seasons. 

"When you know, you know
Then it's time to leave
Like the summer breeze"

So many of my favourite songs by her reference the seasons. Far too many to list. Although of course "Yosemite" does too. But today's quote is from "Paris, Texas" again, the song that I referenced yesterday.

I love this song. 

I am still obsessed with the softness and gentleness of it. Like everything Lana del Rey produces it is so soft and so, so gentle.

This picture reminded me of a summer breeze...

UX Testing

"Writing unit tests for every component ensures that our components work exactly like a user would expect them to work. By utilising unit tests, we can build with confidence and be alerted as soon as some portion of our code breaks out application".

Hmmmyes I see. That sounds hard - and like quite a lot of work, actually. But it makes sense... 

Some other points from my course on this

"Testing helps ensure the functional accuracy of the code that drives the user interface.

By testing individual units of code in isolation, developers can verify that each component or function behaves as intended". 

Also, coming back to the agile principles...

One of the first things I did when I started working in Product (before I started working in tech) was learning about agile principles.

"Testing plays a vital role in facilitating agile development practices, such as continuous integration and continuous delivery".

Writing tests actually improves your codebase

As you start to write tests you have to think more about the logic of your code. This often causes you to break down your "individual code units" into "smaller, testable components".

Types of testing to look out for

• Usability testing
• Functional testing
• Performance testing
• Compatibility testing
• Accessibility testing
• Cross-browser testing
• User Acceptance testing
• Localisation & Internationalisation testing

"Testing should be an ongoing and iterative process".

Common Testing Methodologies

Testing methodologies are so important when building apps. They help to maintain the code and prevent bugs. 

• Unit testing tests individual components, functions or modules in isolation. 
• It helps keep the code correct and maintainable.
• Integration testing tests the relationships between components and modules 
• WOWWW THIS IS SO INTERESTING. THIS IS SO COOL. WOW I NEVER KNEW THAT THIS WAS A THING WOW THANK YOU.
• "It ensures that integrated parts work together seamlessly".
• End-to-End (E2E) Testing
• "End-to-end testing evaluates the complete workflow of an application"
• Functional Testing
• Performance Testing
  
• Speed, responsiveness, and scalability
• Regression Testing
• Visual Regression Testing
• Accessibility Testing
• Cross-Browser and Cross-Device Testing
• "It guarantees a consistent user experience regardless of the platform used".
• Test-Driven Development (TDD) 
• It is a methodology where tests are written first before the code is written.

Unit, Integration and E2E Testing

The three most common tests written out by developers are unit testing, integrating testing, and end-to-end testing.

While unit tests are the cheapest to run and implement, with integration being in the middle, and e2e being the most expensive, it is the opposite when it comes to guaranteeing the usability of your application; the end-to-end tests are the most reliable ones. It is generally recommended to write tests before you write code.

Not only may this save you time when writing code, it will save you time when maintaining code. The fewest amount of tests possible, which cover the most possible scope, is the best ideal. Apparently integration tests are the ones you should be writing the most on. This is because, while unit tests are essential, integration tests strike the balance of coverage and expensiveness.

"Testing is crucial in front-end development to ensure the reliability and functionality of web applications." 

Testing environments

I have to admit that I don't really know what this means. 

My course says that "Creating appropriate test environments is crucial". I don't understand what this environment means.

I don't understand what the "dependencies" are that need to be simulated in my environments.

This could be something to ask on my company's internal questions channel - or my manager, most likely to ask whether it is worth raising this with one of the members of the team.