Git Commands

-
1. git pull # transfer latest build
2. git status # file(build, branch) Status
3. git add . # add all to git ( or git add )
3. git commit –a –m ‘comment’ # comment about push or changes inside a code
4. git push -u origin master # push latest build or latest changes to server


few other commands:
git diff # branch changes
git branch –v # branch
git add test/login/ initializing
git config –global –list

Comments

Post a Comment

Popular posts from this blog

End-to-End Test

-
Image
Definition: End-to-end testing is a methodology used to test whether the flow of an application is performing as designed from start to finish. The purpose of carrying out end-to-end tests is to identify system dependencies and to ensure that the right information is passed between various system components and systems. For example, a simplified end-to-end testing of an email application might involve: 1. Logging in to the application 2. Accessing the inbox 3. Opening and closing the mailbox 4. Composing, forwarding or replying to email 5. Checking the sent items 6. Logging out of the application
Read more

What is Exploratory testing

-
Image
As its name implies, exploratory testing is about exploring, finding out about the software, what it does, what it doesn’t do, what works and what doesn’t work. The tester is constantly making decisions about what to test next and where to spend the (limited) time. This is an approach that is most useful when there are no or poor specifications and when time is severely limited. Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used.
Read more

By my assumption: Why do you need Back End testing:

-
Image
A Back end is the engine of any client/server system. If the back end malfunctions, it may cause system deadlock, data corruption, data loss and bad performance. Many front ends log on to a single SQL server. A bug in a back end may put serious impact on the whole system. Too many bugs in a back end will cost tremendous resources to find and fix bugs and delay the system developments.
Read more