Showing posts with label GIT. Show all posts

Monday, 24 April 2023

How to setup GIT repository in Intelij ?

Pipeline Script Fundamentals

Click Here: DevOps Related Posts

Check GIT commands for Interview preparation SET-1:

GIT Interview Question 1 to 11

Check GIT commands for Interview preparation SET-2:

GIT Interview Question 12 to 21

Check GIT commands for Interview preparation SET-3:

GIT Interview Question 21 to 30

Set up Git repository

Check out a project from a remote host (clone)

IntelliJ IDEA allows you to check out (in Git terms clone) an existing repository and create a new project based on the data you've downloaded.

From the main menu, select Git | Clone, or, if no project is currently opened, click Get from VCS on the Welcome screen.
In the Get from Version Control dialog, specify the URL of the remote repository you want to clone, or select one of the VCS hosting services on the left.
If you are already logged in to the selected hosting service, completion will suggest the list of available repositories that you can clone.

Click Clone. If you want to create a project based on the sources you have cloned, click Yes in the confirmation dialog. Git root mapping will be automatically set to the project root directory.
If your project contains submodules, they will also be cloned and automatically registered as project roots.
When you import or clone a project for the first time, IntelliJ IDEA analyzes it. If the IDE detects more than one configuration (for example, Eclipse and Gradle), it prompts you to select which configuration you want to use.

If the project that you are importing uses a build tool, such as Maven or Gradle, we recommend that you select the build tool configuration.

Select the necessary configuration and click OK.

The IDE pre-configures the project according to your choice. For example, if you select Gradle, IntelliJ IDEA executes its build scripts, loads dependencies, and so on.

Put an existing project under Git version control

You can create a local Git repository based on the existing project sources.

Associate the entire project with a single Git repository

Open the project that you want to put under Git.
Press ⌃ V to open the VCS Operations Popup and select Enable Version Control Integration.

Alternatively, from the main menu, select VCS | Enable Version Control Integration.
Choose Git as the version control system and click OK.
After VCS integration is enabled, IntelliJ IDEA will ask you whether you want to share project settings files via VCS. You can choose Always Add to synchronize project settings with other repository users who work with IntelliJ IDEA.

Associate different directories within the project with different Git repositories

Open the project that you want to put under Git.
From the main menu, choose VCS | Create Git Repository.
In the dialog that opens, specify the directory where a new Git repository will be created.
Git does not support external paths, so if you choose a directory that is outside your project root, make sure that the folder where the repository is going to be created also contains the project root.
If you are creating multiple Git repositories inside the project structure, repeat the previous steps for each directory.

After you have initialized a Git repository for your project, you need to add project files to the repository.

Add files to the local repository

In the Commit tool window ⌘ 0, expand the Unversioned Files node.
Select the files you want to add to Git or the entire changelist and press ⌥ ⌘ A or choose Add to VCS from the context menu.
You can also add files to your local Git repository from the Project tool window: select the files you want to add, and press ⌥ ⌘ A or choose Git | Add from the context menu.

When Git integration is enabled in your project, IntelliJ IDEA suggests adding each newly created file under Git, even if it was added from outside IntelliJ IDEA. You can change this behavior in the Version Control | Confirmation page of the IDE settings ⌘ ,. If you want certain files to always remain unversioned, you can ignore them.

If you attempt to add a file that's on the .gitignore list, IntelliJ IDEA will suggest force adding it. Clicking Cancel in the confirmation dialog only cancels force adding ignored files - all other files will be added to the Git repository.

*******************************************************************

For any doubts or career guidance from me, reach out here : https://topmate.io/sidharth_shukla

********************************************************************

These commands cover a range of basic UI interactions and are a good starting point for building automated tests with Cypress.

Do remember that knowing Linux is one of the most important aspect to work as an SDET.

Basic Linux Commands for Automation QA

****************************************

TOP 15 BDD - CUCUMBER Interview Q&A

************************************************

✍️AUTHOR: LinkedIn Profile

************************************************

Learn (API-Microservice)Testing+ Selenium UI Automation-SDET with Self Paced Videos prepared by FAANG employees and LIVE Doubt Session

*************************************************

SeleniumWebdriver Automation Testing Interview Questions:

https://automationreinvented.blogspot.com/search/label/SeleniumWebdriver

API Testing Interview Question Set:

https://automationreinvented.blogspot.com/2022/03/top-80-api-testing-interview-questions.html

DevOps Interview Q&A:

https://automationreinvented.blogspot.com/2021/11/top-11-devops-interview-questions-and.html

Kubernetes Interview Question Set

https://automationreinvented.blogspot.com/search/label/Kubernetes

Docker Interview Question Set

https://automationreinvented.blogspot.com/Docker

Linux Interview question Set

https://automationreinvented.blogspot.com/search/label/Linux

Automation Testing/SDET Framework Design

https://automationreinvented.blogspot.com/search/label/FrameworkDesign

Java Related Interview Question Set

https://automationreinvented.blogspot.com/search/label/Java

GIT Interview Question Set:

https://automationreinvented.blogspot.com/2021/09/top-40-git-interview-questions-and.html

Coding Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Coding%20Questions

Mobile Testing Interview Question Set:

https://automationreinvented.blogspot.com/search/label/Mobile%20Testing

Python Interview Question Set for QAE - SDET - SDE:

https://automationreinvented.blogspot.com/search/label/Python

Thursday, 12 May 2022

Top 50 GIT Common Interview Q&A on Real Time scenarios for SDET - SDE - QAE? GIT real time scenarios to resolve issues

Pipeline Script Fundamentals

Click Here : DevOps Related Posts

Check GIT commands for Interview preparation SET-1:

GIT Interview Question 1 to 11

Check GIT commands for Interview preparation SET-2:

GIT Interview Question 12 to 21

Check GIT commands for Interview preparation SET-3:

GIT Interview Question 21 to 30

41. How to push code to existing remote branch in Github?

Push your branch to the remote repository:
git push -u origin feature_branch_name

42. How do I force git pull to overwrite the local file changes?

Note: If you have local unpushed commits this will remove them from your branch!

First, run a fetch to update all origin/<branch> refs to latest:(downloads the latest from remote without trying to merge or rebase anything)

git fetch --all

Backup your current branch:

git branch backup-master

Then, you have two options:

git reset --hard origin/master

OR If you are on some other branch:

git reset --hard origin/<branch_name>

//git reset resets the master branch to what you just fetched.

//The --hard option changes all the files in your working tree to match the files in origin/master

WHY AUTOMATION QA SHOULD LEARN GIT?

Git is a powerful version control system that allows developers to manage changes to their codebase. Although Git was originally designed for software development, it has become an essential tool for automation testing as well. Here are some reasons why learning Git is important for automation testing:

Version control: Git helps you keep track of changes to your test code over time. With Git, you can create a repository for your tests, and every time you make changes to your test code, you can commit those changes to the repository. This allows you to revert to an earlier version of your test code if necessary.
Collaboration: Git allows multiple people to work on the same codebase simultaneously. This is useful for automation testing, where multiple testers may need to work on the same set of tests. With Git, testers can work on their own branch of the codebase and merge their changes into the main codebase when they're ready.
Continuous integration: Git integrates well with continuous integration (CI) tools like Jenkins, Travis CI, and CircleCI. These tools allow you to automatically build, test, and deploy your code every time you make changes to the codebase. With Git, you can configure your CI tool to trigger builds and tests whenever changes are pushed to the repository.
Code review: Git allows you to create pull requests, which are requests for other team members to review your code changes. This is a useful feature for automation testing, where it's important to ensure that your tests are of high quality and cover the necessary functionality. Pull requests allow other testers to review your tests and suggest improvements or catch errors.

Overall, Git is an essential tool for automation testing because it allows you to manage changes to your test code, collaborate with other testers, integrate with CI tools, and review code changes. Learning Git will make you a more efficient and effective automation tester.

43. Difference between soft, mixed, and hard resets?

Ans: Click Here For Answer

44. How to undo a git merge with conflicts?

The solution is quite dependent on the version of GIT you are using.

Latest Git Version:

git merge --abort

This attempts to reset your working copy to whatever state it was in before the merge.

Prior to version 1.7.4:

git reset --merge

This is older syntax but does the same as the above.

Prior to version 1.6.2:

git reset --hard

How to integrate Maven project with Jenkins?

ANS: Maven & Jenkins Integration

45. What does cherry-picking a commit with GIT means?

Ans: Let's Consider the following scenario. You have two branches.

a) release2 - This branch is going to your customer, but there are still some bugs to be fixed.

b) master - Classic master branch, where you can for example add functionality for release2.

NOW: You fix something in release2. Of course you need this fix also in master. And that is a typical use-case for cherry picking. So cherry pick in this scenario means that you take a commit from release2 branch and include it into the master branch.

46. Difference between rebase and merge?

Ans: Click Here For Answer

47. How to delete a branch from local and remote?

To delete a local branch you can use below command

git branch -d the_local_branch

To remove a remote branch: be careful while doing this as it will delete a remote branch!

git push origin :the_remote_branch

or use the new syntax (v1.7.0)

git push origin --delete the_remote_branch

48. How to recover the dropped stash in GIT?

Ans: If you know the hash of the stash commit you have dropped, you can apply it as a stash:

git stash apply $stash_hash

49.How to create repository in bitbucket and push code

for automation project?

Ans: Click Here For The Steps

50. What is the meaning of git conflict markers? VERY VERY IMP

Ans: Let's assume that after we pulled from remote branch, we got conflict, when we open the file it looks something like below:

<<<<<<< HEAD:file.txt

Hello world

=======

Adios Amigos

>>>>>>> 77976da35a11db46586:file.txt

A. The lines between the lines beginning <<<<<<< and ======here:

<<<<<<< HEAD:file.txt

Hello world

=======

This above is what we already had locally - you can tell because HEAD points to your current branch or commit.

B. The lines between the beginning ======= and >>>>>>>:

=======

Adios Amigos

>>>>>>> 99976da35a22db46586:file.txt

This is what was introduced by the other (pulled) commit, in this case 99976da35a22

51. Command to delete the file from your working directory and stages the deletion?

Ans: Click Here For Answer

REVISON:

32. How to rename a branch in GIT while working on it?

We can use the below command for renaming of the branch:

git branch -m <new name>

Click Here : DevOps Related Posts

33. If we want to rename the branch from outside the branch then how we can do it?

git branch -m <old name> <new name>

39. How to track the remote branches in GIT?

Assuming there is a remote repository that you cloned your local repository from and also assuming that there is a branch named 'remote_branch' on that remote repository, here is how to track it locally:

# list remote branches

git branch -r

# start tracking one remote branch

git branch --track remote_branch origin/remote_branch

40.How to create repository in bitbucket and push code for automation project?

Ans: Click Here For The Steps

*******************************************************************

For any doubts or career guidance, arrange a 1:1 call with me

https://topmate.io/sidharth_shukla

********************************************************************

Learn (API-Microservice)Testing+(CoreJava+UI)-SDET

with Self Paced Videos and one LIVE Doubt Session