I was curious how the rest of the community tested and deployed NuGet packages to their environments (development, test, quality, production). Specifically, NuGet packages that your company has made. This could be a Core package that all of your other projects rely on.
To give an example, imagine you have a web application. This web application is in the Application repository. If you want to make a change to the web application, it's as simple as checking in your feature to the development branch. Your change will then be reflected on the development environment, on the web application.
Now lets say that this web application consumes a NuGet package that you and your team have developed. Lets call it Core. Core has its own repository. If you want to make a change to Core, you check your feature into the development branch in the Core repository. So now you have a change in Core, but you can't test it because the Web Application is still looking at a different package. In order to actually test your feature in the web application, you'd have to cut a new release and update the package that the web application is using.
This seems like you'd be creating a lot of unnecessary releases and extra effort. I think a stronger approach would be the ability to just check your change into Core and the Web Application would know about it. Then you could instantly test your change. Once enough tested and approved changes go through, we could then cut a release and update the applications with the entire package onto the Test, Quality, and finally Production tiers.
To sum up, I'm really looking for how you and your teams test code that belong in a package, that your application consumes.