How to use New method of redis Package

Best Venom code snippet using redis.New

redis.go

Source: redis.go Github

copy

Full Screen

...18var Redis *RedisClient19/​/​ ConnectRedis 连接 redis 数据库,设置全局的 Redis 对象20func ConnectRedis(address string, username string, password string, db int) {21 once.Do(func() {22 Redis = NewClient(address, username, password, db)23 })24}25/​/​ NewClient 创建一个新的 redis 连接26func NewClient(address string, username string, password string, db int) *RedisClient {27 /​/​ 初始化自定的 RedisClient 实例28 rds := &RedisClient{}29 /​/​ 使用默认的 context30 rds.Context = context.Background()31 /​/​ 使用 redis 库里的 NewClient 初始化连接32 rds.Client = redis.NewClient(&redis.Options{33 Addr: address,34 Username: username,35 Password: password,36 DB: db,37 })38 /​/​ 测试以下连接39 err := rds.Ping()40 logger.LogIf(err)41 return rds42}43/​/​ Ping 用以测试 redis 连接是否正常44func (rds RedisClient) Ping() error {45 _, err := rds.Client.Ping(rds.Context).Result()46 return err...

Full Screen

Full Screen

rate_limiting_test.go

Source: rate_limiting_test.go Github

copy

Full Screen

...5 "github.com/​go-redis/​redis/​v7"6 "github.com/​stretchr/​testify/​assert"7)8const redisURL = "redis:/​/​localhost:6379/​0"9var testInstance = prefixer.NewPrefixer("cozy.example.net", "cozy-example-net")10func TestLoginRateNotExceededMem(t *testing.T) {11 globalCounter = NewMemCounter()12 assert.NoError(t, CheckRateLimit(testInstance, AuthType))13}14func TestLoginRateExceededMem(t *testing.T) {15 globalCounter = NewMemCounter()16 for i := 1; i <= 1000; i++ {17 assert.NoError(t, CheckRateLimit(testInstance, AuthType))18 }19 err := CheckRateLimit(testInstance, AuthType)20 assert.Error(t, err)21}22func TestLoginRateNotExceededRedis(t *testing.T) {23 opts, _ := redis.ParseURL(redisURL)24 client := redis.NewClient(opts)25 client.Del("auth:" + testInstance.DomainName())26 globalCounter = NewRedisCounter(client)27 assert.NoError(t, CheckRateLimit(testInstance, AuthType))28}29func TestLoginRateExceededRedis(t *testing.T) {30 opts, _ := redis.ParseURL(redisURL)31 client := redis.NewClient(opts)32 globalCounter = NewRedisCounter(client)33 client.Del("auth:" + testInstance.DomainName())34 for i := 1; i <= 1000; i++ {35 assert.NoError(t, CheckRateLimit(testInstance, AuthType))36 }37 assert.Error(t, CheckRateLimit(testInstance, AuthType))38}39func Test2FAGenerationNotExceededMem(t *testing.T) {40 globalCounter = NewMemCounter()41 assert.NoError(t, CheckRateLimit(testInstance, TwoFactorGenerationType))42}43func Test2FAGenerationExceededMem(t *testing.T) {44 globalCounter = NewMemCounter()45 for i := 1; i <= 20; i++ {46 assert.NoError(t, CheckRateLimit(testInstance, TwoFactorGenerationType))47 }48 err := CheckRateLimit(testInstance, TwoFactorGenerationType)49 assert.Error(t, err)50}51func Test2FAGenerationNotExceededRedis(t *testing.T) {52 opts, _ := redis.ParseURL(redisURL)53 client := redis.NewClient(opts)54 client.Del("two-factor-generation:" + testInstance.DomainName())55 globalCounter = NewRedisCounter(client)56 assert.NoError(t, CheckRateLimit(testInstance, TwoFactorGenerationType))57}58func Test2FAGenerationExceededRedis(t *testing.T) {59 opts, _ := redis.ParseURL(redisURL)60 client := redis.NewClient(opts)61 globalCounter = NewRedisCounter(client)62 client.Del("two-factor-generation:" + testInstance.DomainName())63 for i := 1; i <= 20; i++ {64 assert.NoError(t, CheckRateLimit(testInstance, TwoFactorGenerationType))65 }66 assert.Error(t, CheckRateLimit(testInstance, TwoFactorGenerationType))67}68func Test2FARateExceededNotExceededMem(t *testing.T) {69 globalCounter = NewMemCounter()70 assert.NoError(t, CheckRateLimit(testInstance, TwoFactorType))71}72func Test2FARateExceededMem(t *testing.T) {73 globalCounter = NewMemCounter()74 for i := 1; i <= 10; i++ {75 assert.NoError(t, CheckRateLimit(testInstance, TwoFactorType))76 }77 err := CheckRateLimit(testInstance, TwoFactorType)78 assert.Error(t, err)79}80func Test2FANotExceededRedis(t *testing.T) {81 opts, _ := redis.ParseURL(redisURL)82 client := redis.NewClient(opts)83 client.Del("two-factor:" + testInstance.DomainName())84 globalCounter = NewRedisCounter(client)85 assert.NoError(t, CheckRateLimit(testInstance, TwoFactorType))86}87func Test2FAExceededRedis(t *testing.T) {88 opts, _ := redis.ParseURL(redisURL)89 client := redis.NewClient(opts)90 globalCounter = NewRedisCounter(client)91 client.Del("two-factor:" + testInstance.DomainName())92 for i := 1; i <= 10; i++ {93 assert.NoError(t, CheckRateLimit(testInstance, TwoFactorType))94 }95 assert.Error(t, CheckRateLimit(testInstance, TwoFactorType))96}...

Full Screen

Full Screen

dao.go

Source: dao.go Github

copy

Full Screen

...11)12/​/​ Dao dao struct .13type Dao struct {14 maxNum int15 expNewArc int16 conf *conf.Config17 redis *redis.Pool18 redisRank *redis.Pool19 redisTag *redis.Pool20 memcache *memcache.Pool21 platform *sql.DB22 /​/​ grpc23 filClient filgrpc.FilterClient24}25/​/​ New init Dao .26func New(c *conf.Config) (d *Dao) {27 d = &Dao{28 conf: c,29 platform: sql.NewMySQL(c.Platform.MySQL),30 maxNum: c.Tag.MaxArcsLimit,31 redis: redis.NewPool(c.Redis.Rank.Redis),32 redisRank: redis.NewPool(c.RedisRank),33 redisTag: redis.NewPool(c.RedisTag),34 memcache: memcache.NewPool(c.Memcache),35 expNewArc: int(time.Duration(c.Redis.Rank.Expire.TagNewArc) /​ time.Second),36 }37 var err error38 if d.filClient, err = filgrpc.NewClient(c.FilterGRPC); err != nil {39 panic(err)40 }41 return42}43/​/​ PingRedis ping redis .44func (d *Dao) pingRedis(c context.Context) (err error) {45 conn := d.redis.Get(c)46 _, err = conn.Do("SET", "PING", "PONG")47 conn.Close()48 return49}50/​/​ pingRedisRank ping rank redis .51func (d *Dao) pingRedisRank(c context.Context) (err error) {52 conn := d.redisRank.Get(c)...

Full Screen

Full Screen

Blogs

Check out the latest blogs from LambdaTest on this topic:

How Testers Can Remain Valuable in Agile Teams

Traditional software testers must step up if they want to remain relevant in the Agile environment. Agile will most probably continue to be the leading form of the software development process in the coming years.

Fault-Based Testing and the Pesticide Paradox

In some sense, testing can be more difficult than coding, as validating the efficiency of the test cases (i.e., the ‘goodness’ of your tests) can be much harder than validating code correctness. In practice, the tests are just executed without any validation beyond the pass/fail verdict. On the contrary, the code is (hopefully) always validated by testing. By designing and executing the test cases the result is that some tests have passed, and some others have failed. Testers do not know much about how many bugs remain in the code, nor about their bug-revealing efficiency.

Introducing LambdaTest Analytics: Test Reporting Made Awesome ????

Collecting and examining data from multiple sources can be a tedious process. The digital world is constantly evolving. To stay competitive in this fast-paced environment, businesses must frequently test their products and services. While it’s easy to collect raw data from multiple sources, it’s far more complex to interpret it properly.

Putting Together a Testing Team

As part of one of my consulting efforts, I worked with a mid-sized company that was looking to move toward a more agile manner of developing software. As with any shift in work style, there is some bewilderment and, for some, considerable anxiety. People are being challenged to leave their comfort zones and embrace a continuously changing, dynamic working environment. And, dare I say it, testing may be the most ‘disturbed’ of the software roles in agile development.

Testing in Production: A Detailed Guide

When most firms employed a waterfall development model, it was widely joked about in the industry that Google kept its products in beta forever. Google has been a pioneer in making the case for in-production testing. Traditionally, before a build could go live, a tester was responsible for testing all scenarios, both defined and extempore, in a testing environment. However, this concept is evolving on multiple fronts today. For example, the tester is no longer testing alone. Developers, designers, build engineers, other stakeholders, and end users, both inside and outside the product team, are testing the product and providing feedback.

Automation Testing Tutorials

Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.

LambdaTest Learning Hubs:

YouTube

You could also refer to video tutorials over LambdaTest YouTube channel to get step by step demonstration from industry experts.

Run Venom automation tests on LambdaTest cloud grid

Perform automation testing on 3000+ real desktop and mobile devices online.

Try LambdaTest Now !!

Get 100 minutes of automation test minutes FREE!!

Next-Gen App & Browser Testing Cloud

Was this article helpful?

Helpful

NotHelpful