Software de alta calidad

Software de alta calidad

6c137ee3013821b517c4b9beed0145df?s=128

Fernando Perales

May 30, 2017
Tweet

Transcript

  1. 2.
  2. 3.

    Ingenierio de Software ex Crowd Interactive / MagmaLabs / FreeAgent

    Software Promotor del FLOSS Amante del Heavy Metal y la cerveza Instructor de Ruby on Rails en Platzi Anfitrión de la comunidad RubyGDL Fundador de elbuencodigo.com Fan de Gregory Sallust
  3. 4.
  4. 8.

    “Es un enfoque colaborativo para definir requetimientos y pruebas funcionales

    orientadas al negocio para productos de software con base en capturar e ilustrar los requerimientos usando ejemplos reales en lugar de sentencias abstractas”
  5. 11.
  6. 12.

    Feature: Login In order to use the application As a

    user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
  7. 13.
  8. 14.

    “Es un lenguaje de dominio específico, leíble desde el lago

    de negocios que permite describir el funcionamiento del software sin detallar cómo será implementado”
  9. 17.

    “Una holística y flexicle estrategia de desarrollo de producto donde

    un equipo de desarrollo trabaja como una unidad para alcanzar un objetivo común "
  10. 23.

    “Una comprensible lista de tareas, expresadas en orden de importancia

    para el negocio y cuánto valor aportan al mismo”
  11. 26.

    “Un sistema que guarda los cambios hechos a un archivo

    o conjunto de archivos a través del tiempo”
  12. 30.

    “Una metodología de pruebas de software en la que las

    unidades individuales de código son probadas para determinar si son aptas para ser utilizadas”
  13. 32.

    class User < ActiveRecord::Base # Método que prueba si un

    usuario tiene una cuenta de HackerGarage def has_hackergarare_account? !!self. email.match(/@hackergarage.mx$/) end end
  14. 33.

    require 'rails_helper' describe User do let(:user_with_hackergarage_account) { User.create email: 'demo@hackergarage.mx'

    } let(:user_with_gmail_account) { User.create email: 'demo@gmail.com' } describe '.has_hackergarage_account?' do it 'returns true when email ends with "@hackergarage.mx"' do expect( user_with_hackergarage_account.has_magmalabs_account? ).to be true end it 'returns false when email ends with "other domain"' do expect( user_with_gmail_account.has_hackergarage_account? ).to be false end end end
  15. 34.
  16. 36.

    “La fase de pruebas de software en la cual las

    unidades individuales se combinan y prueban como un grupo”
  17. 39.

    “Un método de pruebas en el que se utilizan ejemplos

    para describir el comportamiento de la aplicación o el comportamiento de la misma”
  18. 41.

    Feature: Login In order to use the application As a

    user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
  19. 43.

    Feature: Login In order to use the application As a

    user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
  20. 45.

    Feature: Login In order to use the application As a

    user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
  21. 46.

    And(/^I have entered (.*) as my username$/) do |username| fill_in

    'user[login]', with: username end And(/^I have entered (.*) as my password$/) do |password| fill_in 'user[password]', with: password end
  22. 47.

    Feature: Login In order to use the application As a

    user I want to be able to login Scenario: with invalid credentials Given I visit the / page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be shown a message error Scenario: with valid credentials Given I have created an account in the past And I visit the /events page And I have entered demo as my username And I have entered demo1234 as my password When I press Sign in Then I will be redirected to events page
  23. 48.

    Given(/^I have created an account in the past$/) do @user

    = FactoryGirl.create :user, username: 'demo', password: 'demo1234' End Then(/^I will be shown a message error$/) do expect(page).to have_content 'Invalid login or password.' end When(/^I press Sign in$/) do click_button 'Sign in' end Then(/^I will be redirected to home page$/) do expect(page).to have_content 'Login successful' end Then(/^I will be redirected to (.*) page$/) do |url| path = URI.parse(current_url).path expect(path).to match "/#{url}" end
  24. 51.
  25. 54.
  26. 56.
  27. 58.

    role :demo, %w{example.com example.org example.net} task :uptime do on roles(:demo),

    in: :parallel do |host| uptime = capture(:uptime) puts "#{host.hostname} reports: #{uptime}" end end
  28. 62.

    “Continuous Integration is the practice of merging development work with

    a Master/Trunk/Mainline branch constantly so that you can test changes, and test that changes work with other changes” http://blog.assembla.com/AssemblaBlog/tabid/12618/bid/92411/Continu ous-Delivery-vs-Continuous-Deployment-vs-Continuous-Integration-Wait- huh.aspx
  29. 63.

    “Continuous Delivery is the continual delivery of code to an

    environment once the developer feels the code is ready to ship.” http://blog.assembla.com/AssemblaBlog/tabid/12618/bid/92411/Continu ous-Delivery-vs-Continuous-Deployment-vs-Continuous-Integration-Wait- huh.aspx
  30. 64.

    “Continuous Deployment is the deployment or release of code to

    Production as soon as it is ready” http://blog.assembla.com/AssemblaBlog/tabid/12618/bid/92411/Continu ous-Delivery-vs-Continuous-Deployment-vs-Continuous-Integration-Wait- huh.aspx
  31. 69.
  32. 72.
  33. 75.

    scss_files: "**/*.scss" linters: BangFormat: enabled: true space_before_bang: true space_after_bang: false

    BorderZero: enabled: true convention: zero # or `none` ColorKeyword: enabled: true ColorVariable: enabled: true Comment: enabled: true DebugStatement: enabled: true
  34. 76.
  35. 80.
  36. 83.
  37. 86.
  38. 87.