Skip to content
Snippets Groups Projects
Select Git revision
  • ag-test
  • rs-test
  • master default protected
  • test-me-pa
  • mksionek-master-patch-52381
  • new-branch-10
  • test-conflicts
  • test-suggestions
  • alejandro-test
  • patch-25
  • winh-test-image-doscussion
  • stg-lfs-image-test-2
  • stg-lfs-image-test
  • test42016
  • issue_42016
  • issue-32709
  • add-codeowners
  • ClemMakesApps-master-patch-62759
  • bvl-staging-test
  • bvl-merge-base-api
  • v9.2.0-rc6 protected
  • v9.2.0-rc5 protected
  • v9.2.0-rc4 protected
  • v9.2.0-rc3 protected
  • v9.1.4 protected
  • v9.2.0-rc2 protected
  • v9.2.0-rc1 protected
  • v9.1.3 protected
  • v8.17.6 protected
  • v9.0.7 protected
  • v9.1.2 protected
  • v9.1.1 protected
  • v9.2.0.pre protected
  • v9.1.0 protected
  • v9.1.0-rc7 protected
  • v9.1.0-rc6 protected
  • v9.0.6 protected
  • v9.1.0-rc5 protected
  • v9.1.0-rc4 protected
  • v9.1.0-rc3 protected
40 results

variables_spec.rb

Blame
    • Grzegorz Bizon's avatar
      2240807c
      Assume that unspecified CI config is undefined · 2240807c
      Grzegorz Bizon authored
      We assume that when someone adds a key for the configuration entry, but
      does not provide a valid value, which causes entry to be `nil`, then
      entry should be considered as the undefined one. We also assume this is
      semantically correct, this is also backwards compatible with legacy CI
      config processor.
      
      See issue #18775 for more details.
      2240807c
      History
      Assume that unspecified CI config is undefined
      Grzegorz Bizon authored
      We assume that when someone adds a key for the configuration entry, but
      does not provide a valid value, which causes entry to be `nil`, then
      entry should be considered as the undefined one. We also assume this is
      semantically correct, this is also backwards compatible with legacy CI
      config processor.
      
      See issue #18775 for more details.
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    variables_spec.rb 1.07 KiB
    require 'spec_helper'
    
    describe Gitlab::Ci::Config::Node::Variables do
      let(:entry) { described_class.new(config) }
    
      describe 'validations' do
        context 'when entry config value is correct' do
          let(:config) do
            { 'VARIABLE_1' => 'value 1', 'VARIABLE_2' => 'value 2' }
          end
    
          describe '#value' do
            it 'returns hash with key value strings' do
              expect(entry.value).to eq config
            end
          end
    
          describe '#errors' do
            it 'does not append errors' do
              expect(entry.errors).to be_empty
            end
          end
    
          describe '#valid?' do
            it 'is valid' do
              expect(entry).to be_valid
            end
          end
        end
    
        context 'when entry value is not correct' do
          let(:config) { [ :VAR, 'test' ] }
    
          describe '#errors' do
            it 'saves errors' do
              expect(entry.errors)
                .to include /should be a hash of key value pairs/
            end
          end
    
          describe '#valid?' do
            it 'is not valid' do
              expect(entry).not_to be_valid
            end
          end
        end
      end
    end