redigomock: github.com/rafaeljusto/redigomock Index | Files

package redigomock

import "github.com/rafaeljusto/redigomock"

Package redigomock is a mock for redigo library (redis client)

Redigomock basically register the commands with the expected results in a internal global variable. When the command is executed via Conn interface, the mock will look to this global variable to retrieve the corresponding result.

To start a mocked connection just do the following:

c := redigomock.NewConn()

Now you can inject it whenever your system needs a redigo.Conn because it satisfies all interface requirements. Before running your tests you need beyond of mocking the connection, registering the expected results. For that you can generate commands with the expected results.

c.Command("HGETALL", "person:1").Expect("Person!")
c.Command(
  "HMSET", []string{"person:1", "name", "John"},
).Expect("ok")

As the Expect method from Command receives anything (interface{}), another method was created to easy map the result to your structure. For that use ExpectMap:

c.Command("HGETALL", "person:1").ExpectMap(map[string]string{
  "name": "John",
  "age": 42,
})

You should also test the error cases, and you can do it in the same way of a normal result.

c.Command("HGETALL", "person:1").ExpectError(fmt.Errorf("Low level error!"))

Sometimes you will want to register a command regardless the arguments, and you can do it with the method GenericCommand (mainly with the HMSET).

c.GenericCommand("HMSET").Expect("ok")

All commands are registered in a global variable, so they will be there until all your test cases ends. So for good practice in test writing you should in the beginning of each test case clear the mock states.

c.Clear()

Let's see a full test example. Imagine a Person structure and a function that pick up this person in Redis using redigo library (file person.go):

package person

import (
  "fmt"
  "github.com/gomodule/redigo/redis"
)

type Person struct {
  Name string `redis:"name"`
  Age  int    `redis:"age"`
}

func RetrievePerson(conn redis.Conn, id string) (Person, error) {
  var person Person

  values, err := redis.Values(conn.Do("HGETALL", fmt.Sprintf("person:%s", id)))
  if err != nil {
    return person, err
  }

  err = redis.ScanStruct(values, &person)
  return person, err
}

Now we need to test it, so let's create the corresponding test with redigomock (fileperson_test.go):

package person

import (
  "github.com/rafaeljusto/redigomock"
  "testing"
)

func TestRetrievePerson(t *testing.T) {
  conn := redigomock.NewConn()
  cmd := conn.Command("HGETALL", "person:1").ExpectMap(map[string]string{
    "name": "Mr. Johson",
    "age":  "42",
  })

  person, err := RetrievePerson(conn, "1")
  if err != nil {
    t.Fatal(err)
  }

  if conn.Stats(cmd) != 1 {
    t.Fatal("Command was not called!")
  }

  if person.Name != "Mr. Johson" {
    t.Errorf("Invalid name. Expected 'Mr. Johson' and got '%s'", person.Name)
  }

  if person.Age != 42 {
    t.Errorf("Invalid age. Expected '42' and got '%d'", person.Age)
  }
}

func TestRetrievePersonError(t *testing.T) {
  conn := redigomock.NewConn()
  conn.Command("HGETALL", "person:1").ExpectError(fmt.Errorf("Simulate error!"))

  person, err = RetrievePerson(conn, "1")
  if err == nil {
    t.Error("Should return an error!")
  }
}

When you use redis as a persistent list, then you might want to call the same redis command multiple times. For example:

func PollForData(conn redis.Conn) error {
  var url string
  var err error

  for {
    if url, err = conn.Do("LPOP", "URLS"); err != nil {
      return err
    }

    go func(input string) {
      // do something with the input
    }(url)
  }

  panic("Shouldn't be here")
}

To test it, you can chain redis responses. Let's write a test case:

func TestPollForData(t *testing.T) {
  conn := redigomock.NewConn()
  conn.Command("LPOP", "URLS").
    Expect("www.some.url.com").
    Expect("www.another.url.com").
    ExpectError(redis.ErrNil)

  if err := PollForData(conn); err != redis.ErrNil {
    t.Error("This should return redis nil Error")
  }
}

In the first iteration of the loop redigomock would return "www.some.url.com", then "www.another.url.com" and finally redis.ErrNil.

Sometimes providing expected arguments to redigomock at compile time could be too constraining. Let's imagine you use redis hash sets to store some data, along with the timestamp of the last data update. Let's expand our Person struct:

type Person struct {
  Name      string `redis:"name"`
  Age       int    `redis:"age"`
  UpdatedAt uint64 `redis:updatedat`
  Phone     string `redis:phone`
}

And add a function updating personal data (phone number for example). Please notice that the update timestamp can't be determined at compile time:

func UpdatePersonalData(conn redis.Conn, id string, person Person) error {
  _, err := conn.Do("HMSET", fmt.Sprint("person:", id), "name", person.Name, "age", person.Age, "updatedat" , time.Now.Unix(), "phone" , person.Phone)
  return err
}

Unit test:

func TestUpdatePersonalData(t *testing.T){
  redigomock.Clear()

  person := Person{
    Name  : "A name",
    Age   : 18
    Phone : "123456"
  }

  conn := redigomock.NewConn()
  conn.Commmand("HMSET", "person:1", "name", person.Name, "age", person.Age, "updatedat", redigomock.NewAnyInt(), "phone", person.Phone).Expect("OK!")

  err := UpdatePersonalData(conn, "1", person)
  if err != nil {
    t.Error("This shouldn't return any errors")
  }
}

As you can see at the position of current timestamp redigomock is told to match AnyInt struct created by NewAnyInt() method. AnyInt struct will match any integer passed to redigomock from the tested method. Please see fuzzyMatch.go file for more details.

Index

Package Files

command.go doc.go fuzzy_match.go redigomock.go

type Cmd Uses

type Cmd struct {
    Name      string        // Name of the command
    Args      []interface{} // Arguments of the command
    Responses []Response    // Slice of returned responses
    Called    bool          // State for this command called or not
}

Cmd stores the registered information about a command to return it later when request by a command execution

func (*Cmd) Expect Uses

func (c *Cmd) Expect(response interface{}) *Cmd

Expect sets a response for this command. Every time a Do or Receive method is executed for a registered command this response or error will be returned. Expect call returns a pointer to Cmd struct, so you can chain Expect calls. Chained responses will be returned on subsequent calls matching this commands arguments in FIFO order

func (*Cmd) ExpectError Uses

func (c *Cmd) ExpectError(err error) *Cmd

ExpectError allows you to force an error when executing a command/arguments

func (*Cmd) ExpectMap Uses

func (c *Cmd) ExpectMap(response map[string]string) *Cmd

ExpectMap works in the same way of the Expect command, but has a key/value input to make it easier to build test environments

func (*Cmd) ExpectSlice Uses

func (c *Cmd) ExpectSlice(resp ...interface{}) *Cmd

ExpectSlice makes it easier to expect slice value e.g - HMGET command

func (*Cmd) ExpectStringSlice Uses

func (c *Cmd) ExpectStringSlice(resp ...string) *Cmd

ExpectStringSlice makes it easier to expect a slice of strings, plays nicely with redigo.Strings

type Conn Uses

type Conn struct {
    SubResponses []Response   // Queue responses for PubSub
    ReceiveWait  bool         // When set to true, Receive method will wait for a value in ReceiveNow channel to proceed, this is useful in a PubSub scenario
    ReceiveNow   chan bool    // Used to lock Receive method to simulate a PubSub scenario
    CloseMock    func() error // Mock the redigo Close method
    ErrMock      func() error // Mock the redigo Err method
    FlushMock    func() error // Mock the redigo Flush method

    Errors []error // Storage of all error occured in do functions
    // contains filtered or unexported fields
}

Conn is the struct that can be used where you inject the redigo.Conn on your project

func NewConn Uses

func NewConn() *Conn

NewConn returns a new mocked connection. Obviously as we are mocking we don't need any Redis connection parameter

func (*Conn) AddSubscriptionMessage Uses

func (c *Conn) AddSubscriptionMessage(msg interface{})

AddSubscriptionMessage register a response to be returned by the receive call.

func (*Conn) Clear Uses

func (c *Conn) Clear()

Clear removes all registered commands. Useful for connection reuse in test scenarios

func (*Conn) Close Uses

func (c *Conn) Close() error

Close can be mocked using the Conn struct attributes

func (*Conn) Command Uses

func (c *Conn) Command(commandName string, args ...interface{}) *Cmd

Command register a command in the mock system using the same arguments of a Do or Send commands. It will return a registered command object where you can set the response or error

func (*Conn) Do Uses

func (c *Conn) Do(commandName string, args ...interface{}) (reply interface{}, err error)

Do looks in the registered commands (via Command function) if someone matches with the given command name and arguments, if so the corresponding response or error is returned. If no registered command is found an error is returned

func (*Conn) DoWithTimeout Uses

func (c *Conn) DoWithTimeout(readTimeout time.Duration, cmd string, args ...interface{}) (interface{}, error)

DoWithTimeout is a helper function for Do call to satisfy the ConnWithTimeout interface.

func (*Conn) Err Uses

func (c *Conn) Err() error

Err can be mocked using the Conn struct attributes

func (*Conn) ExpectationsWereMet Uses

func (c *Conn) ExpectationsWereMet() error

ExpectationsWereMet can guarantee that all commands that was set on unit tests called or call of unregistered command can be caught here too

func (*Conn) Flush Uses

func (c *Conn) Flush() error

Flush can be mocked using the Conn struct attributes

func (*Conn) GenericCommand Uses

func (c *Conn) GenericCommand(commandName string) *Cmd

GenericCommand register a command without arguments. If a command with arguments doesn't match with any registered command, it will look for generic commands before throwing an error

func (*Conn) Receive Uses

func (c *Conn) Receive() (reply interface{}, err error)

Receive will process the queue created by the Send method, only one item of the queue is processed by Receive call. It will work as the Do method

func (*Conn) ReceiveWithTimeout Uses

func (c *Conn) ReceiveWithTimeout(timeout time.Duration) (interface{}, error)

ReceiveWithTimeout is a helper function for Receive call to satisfy the ConnWithTimeout interface.

func (*Conn) Script Uses

func (c *Conn) Script(scriptData []byte, keyCount int, args ...interface{}) *Cmd

Script registers a command in the mock system just like Command method would do. The first argument is a byte array with the script text, next ones are the ones you would pass to redis Script.Do() method

func (*Conn) Send Uses

func (c *Conn) Send(commandName string, args ...interface{}) error

Send stores the command and arguments to be executed later (by the Receive function) in a first-come first-served order

func (*Conn) Stats Uses

func (c *Conn) Stats(cmd *Cmd) int

Stats returns the number of times that a command was called in the current connection

type FuzzyMatcher Uses

type FuzzyMatcher interface {

    // Match takes an argument passed to mock connection Do call and checks if
    // it fulfills constraints set in concrete implementation of this interface
    Match(interface{}) bool
}

FuzzyMatcher is an interface that exports one function. It can be passed to the Command as an argument. When the command is evaluated against data provided in mock connection Do call, FuzzyMatcher will call Match on the argument and return true if the argument fulfills constraints set in concrete implementation

func NewAnyData Uses

func NewAnyData() FuzzyMatcher

NewAnyData returns a FuzzyMatcher instance matching every data type passed as an argument (returns true by default)

func NewAnyDouble Uses

func NewAnyDouble() FuzzyMatcher

NewAnyDouble returns a FuzzyMatcher instance matching any double passed as an argument

func NewAnyInt Uses

func NewAnyInt() FuzzyMatcher

NewAnyInt returns a FuzzyMatcher instance matching any integer passed as an argument

type Response Uses

type Response struct {
    Response interface{} // Response to send back when this command/arguments are called
    Error    error       // Error to send back when this command/arguments are called
}

Response struct that represents single response from `Do` call

Package redigomock imports 6 packages (graph) and is imported by 6 packages. Updated 2019-02-02. Refresh now. Tools for package owners.