rcoproc

#GIT

Estados

• Modificado (modified);
• Preparado (staged/index)
• Consolidado (comitted);

Ajuda

rcoproc

Rails Generating & Scaffolding

Rails' use of strict naming conventions means a lot of core code SHOULD be in the same format whoever writes it? It could be written by a friend, colleague or a computer... it shouldn't matter because the same Rails rules apply to everyone.

This means that Rails can actually do some tasks for you! It can actually build things and write code on your behalf...

Coming from another language like PHP, this can seem like magic.

rcoproc

#!/usr/bin/env bash

# https://docs.docker.com/install/linux/docker-ce/ubuntu/
sudo apt-get install apt-transport-https ca-certificates curl software-properties-common
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable"
sudo apt-get update
sudo apt-get install docker-ce

# https://docs.docker.com/compose/install/

rcoproc

# This is a skeleton for testing models including examples of validations, callbacks,
# scopes, instance & class methods, associations, and more.
# Pick and choose what you want, as all models don't NEED to be tested at this depth.
#
# I'm always eager to hear new tips & suggestions as I'm still new to testing,
# so if you have any, please share!
#
# @kyletcarlson
#
# This skeleton also assumes you're using the following gems: 

rcoproc

=Navigating=
    visit('/projects')
    visit(post_comments_path(post))

=Clicking links and buttons=
    click_link('id-of-link')
    click_link('Link Text')
    click_button('Save')
    click('Link Text') # Click either a link or a button
    click('Button Value')

rcoproc

require 'rails_helper'

RSpec.describe TodosController, :type => :controller do

  describe "GET #index" do
  #describe "POST #create" do
  #describe "GET #show" do
  #describe "PATCH #update" do (or PUT #update)
  #describe "DELETE #destroy" do
  #describe "GET #new" do

rcoproc

# Padrâo xUnit 4 fases de teste(4 Standard test phases XUnit)
# Setup
# Exercise
# Verify
# Teardown

# "Stubs são para a fase de Setup" - "Stubs are for the Setup phase"
# "Stubs são usados para substituir estados." - " Stubs are used to replace state"

require 'student'

rcoproc

# Quando você precisa atribuir uma variável, ao invés de usar um bloco before para
# criar uma variável de instância, use let.
# Ao usar let, a variável é carregada apenas quando ela é utilizada pela primeira vez
# no teste e fica na cache até o teste em questão terminar.

$counter = 0

describe "let" do
  let(:count) { $counter += 1 }

rcoproc

# Você pode usar let! Para forçar a
# invocação do método/helper antes
# de cada teste.

$count = 0

describe "let!" do
  ordem_de_invocacao = []

  let!(:contador) do

rcoproc

# Padrâo xUnit 4 fases de teste - 4 Standard test phases XUnit
# Setup
# Exercise
# Verify
# Teardown


# "Mocks são para a fase de Verify" - "Mocks are for the Verify stage" 
# "Mocks são usados para testar comportamentos" - "Mocks are used to test behaviors"