Ghanendra's Tips

Pretty much all the Sitecore development is happening in Agile. Hence, code is released more frequently to live servers than it used to be in waterfall models. This also means there is a need of testing after each release. A regression in QA environment and a smoke test in STAGE environment is required to ensure that the development done in sprint does not break any thing else. This is the job of QA team. Why are we talking about it here? If your team is testing Sitecore functionalities manually, then it is wise to automate at least some of your test cases. Testing some basic Sitecore functionalities like login, publishing etc. manually is something QA team can easily do but when one needs to automate it, QA developers needs to have some knowledge of Sitecore also and vice-versa.  Hence, here is a simple blog on guiding how to develop some basic automated test cases in Sitecore. Lets get started.. In this blog, I am taking example of a basic scenario which includes testing that your us

Hello friends! In this blog I am going to talk about fundamentals of Azure Functions.  Azure Functions is a server less solution that allows you to write less code, maintain less infrastructure, and save on costs. Instead of worrying about deploying and maintaining servers, the cloud infrastructure provides all the up-to-date resources needed to keep your applications running. Hence, main advantages of Azure Functions are -  serverless programming highly scalable low cost Azure Functions can be look on as Events + Code which means all we have to do is to write code and then tell Azure what trigger will run the code. A trigger can be a scheduler, a message in MessageQueue, a new item in blob storage, a http request etc. So how do we run code in Azure - Azure VM install whatever u want web servers, windows services etc IaaS complete control of the serverless choose your operating system You are responsible patching and maintaining scaling operational ov