- Location - The location of the application. Usually just a URL, but the location can contain multiple pieces of information that can be used by an app
- pathname - The "file/directory" portion of the URL, like
invoices/123 - search - The stuff after
?in a URL like/assignments?showGrades=1. - query - A parsed version of search, usually an object but not a standard browser feature.
- hash - The
#portion of the URL. This is not available to servers inrequest.urlso its client only. By default it means which part of the page the user should be scrolled to, but developers use it for various things. - state - Object associated with a location. Think of it like a hidden URL query. It's state you want to keep with a specific location, but you don't want it to be visible in the URL.
- pathname - The "file/directory" portion of the URL, like
"Why test your code? So you know it can work, and have a way to quickly verify it still works as it evolves." - some engineer on Quora.
For more info: https://en.wikipedia.org/wiki/Test-driven_development
The overriding thought for testing should be "What tests need to pass in order to ensure my code works as expected?". For both services and libraries, arguably the highest priority are interface tests since they are the specific contract between an application and its end-users.
OlderNewer
