pattnaik-soumitri/testing

L2 or Above

Tell us about your project and your roles and responsibility in that project.

About Project

Currently I am working on a healthcare application named Caren. In th United States, there are more than 49% of families where both married-couples are working. In such families it becomes difficult for the couples to take care of their elders (parents, grand parent, in laws etc.). To solve this problem US has many home healthcare providers called hospices, for the elders to live. Hospices have trained professionals called care givers who usually take care of the elderly person(s). In the Unites States more than 70% of the people older than 60 years are having at least two health conditions, so it becomes extremely important for the hospices to provide means to start or continue diagnosis, monitor the vitals (etc) for the elders.

That's where Caren comes into the picture. In Caren the caregivers or the elders themselves (elders are called Patient in Caren) use our apps (mobile and web) to :
- Track patient's vitals such as BP, Glucose level, SpO2 level, Body temperature, Pain level etc.
- Manage meals and medication timings.
- Track health conditions, observations, side effects, Emergency Room Visits, Vaccinations etc.
Caregivers or the patients themselves can enter their readings and observations and doctors and other family members of their family can monitor their loved ones in Caren.

Mention the followings if asked for more details
- Caren also has Interoperability where it can automatically sync readings for patients who are using iHealth or Omoron health care devices (iHealth and Omoron are health care device manufacturer).
- We are currently working EHR (Electronic Health Record) interoperability. We are currently working with Cerner EHR where doctors / hospitals using Cerner EHR can have their patient's vitals and observations being taken and synced to the EHR seamlessly from home using Caren app.
- We have functionality in the app to manage legal documents such as insurances, wills etc.
Roles & Responsibilities

Goes here
So you developed the framework or you just work on existing framework?
Which methodology you use in your framework? Why?
Explain BDD, TDD.
- link 1
- link 2
- link 3
Explain your framework structure/modules.
Explain your framework execution flow.
What is page object model?
How you use those objects in your test scripts?
How you generate reports?
How you generate logs?
You just told that you use java in your project, for what propose you use java?
You just told that you use selenium in your project, for what propose you use selenium?
You just told that you use testNG in your project, for what propose you use testNG?
You just told that you use cucumber in your project, for what propose you use cucumber?
You just told that you use maven in your project, for what propose you use maven?
How you inject dependencies in your framework? You add .jar files or you inject in to your POM.xml file?

We use maven, so we add our dependencies to the POM.xml file. So we do not add jar files manually. In the POM.xml file there is a <dependencies></dependencies> tag, inside which each dependency is defined.

Example:
```
<dependencies>
    <dependency>
        <groupId>org.seleniumhq.selenium</groupId>
        <artifactId>selenium-java</`artifactId>
        <version>3.141.59</version>`
    </dependency>
    .
    .
    .
    // Other dependencies go here
</dependencies>
```
What plugin or dependencies you use in your frame work?
How you test or build or run your automation framework?
What tools you use for CI-CD?

Jenkins
Can you just explain your ci-cd flow?

We use Jenkins for automatic and manual build and deployments. We have mainly three important branches for our source repositories i.e. master, staging and test. When a developers gets assigned to a JIRA ticket (lets say IA-100), they create feature (feature/IA-100) branches from the test branch. Then the developer makes code changes for the ticket, does testing on the local then pushes the code to the feature branch. As soon as code is pushed to a feature branch, Jenkins automatically create a build from that feature branch (feature/IA-100) and deploys that to the DEV server. Then the developer performs functional testing on the DEV environment. If all look good, then he creates a PR from the feature branch to the test branch (feature/IA-100 --> test). Then the PR gets peer reviewed by the other developers and finally the developer merges it to the test branch. As soon as there is any new code change to the test branch, Jenkins automatically creates a build from the test branch and deploys that to the TEST environment. At that point the ticket is Ready For QA. We perform QA testing on the TEST environment and if found a bug it is raised and the same process is continued. Once the feature is completely tested, the QA person creates a PR from TEST branch to staging branch (TEST --> staging). Just like before, as soon as the code is merged to staging branch, the build is created and deployed to STAGING environment. Regression and UAT is performed on the STAGING branch and finally a PR from staging branch to master is created, merging which automatically builds and deploys to PRODUCTION environment.
You use Jenkins? Can you configure with your framework?

Yes, I use Jenkins. We have Jenkins auto triggers to automatically build and deploy to different environments when code is pushed / merged to different branches (explained in the above question). I use Jenkins to manually build and deploy. It is a two step process.
1. Build
2. Deploy
To build I go to the build job, put the branch name which I want to build as parameter and click on build. This will create a build out of the source code. To deploy, I just go to the deploy job, select the environment from the parameter drop down, put down the build number to the parameter and click on 'Build'.

I don't know how to configure Jenkins, that is something our DevOps team does.
What is difference between src/main/java and src/test/java?

If we are using maven or gradle as our build tool, they consider src/test/java package to contain the automated test cases and src/main/java to contains the actual code. We do not want to ship the automated test cases to production as they are not part of the actual application used by the users. Maven/gradle do not include the code under src/test/java to the final build file which keeps the build size down and enables faster uploading. stackoverflow link.
Where from you getting the test data, you use excel, csv or database? How?
Do you follow agile? How?
Who you report your issues?
How and where you report a bug or error?
So you mentioned in your resume you are involved in Test Planning , Story analysis can you explain what is your contribution to Test Planning , Story analysis .
So you have written scenarios, test case and steps, can you explain with an example you have written for your project?
So you have written scenarios, test case and steps, I am giving you a webpage for a login function, please tell me what you will write.
What are the challenges faced in your project?
The challenges you just told us can you explain how you handled or tackled, with an example.
What is your team size? What is your roles and responsibility?
Who are the team members?
What you do if a merge conflict raises?
On the day one of joining a company what will your approach as an automation tester? You directly write automation script, you write test cases?

L2 or Above

About