realm

接口测试与Postman

允我心安 提交于 2021-01-07 00:54:54
阅读目录 1. 接口测试简介 1.1 什么是接口测试    1.2 接口测试的必要性    1.3 接口测试流程    1.4 接口文档    1.5 接口测试用例设计    1.6 接口测试用例模板 2.Postman    2.1 Postman简介    2.2 Postman主页    2.3 Postman 发送请求    2.4 Postman 授权    2.5 Cookie设置    2.6 Postman变量    2.7 Postman断言    2.8 postman运行collection    2.9 Postman数据驱动    2.10 构建工作流 1.接口测试简介 1.1 什么是接口测试 测试人员通常所说的“接口测试”是针对系统各组件之间接口的一种测试,它属于功能测试。接口能测出普通界面操作难以发现的问题。如,我们都知道系统是由前端后端组成,一些数据在前端做了校验,后端同样也需要校验才能保证安全,界面操作显然只能检查到前端校验这一层,只有直接面对前后端之间的该接口才能检验出后端是否也做了校验。 1.2 接口测试的必要性   • 可以发现很多页面操作发现不了的问题     • 检查系统的异常处理能力   • 检查系统的安全性、稳定性          • 前端随便变,接口测好了,后端不用变 1.3 接口测试的流程   • 需求评审,熟悉业务和需求   

Empty object user when authenticating with Realm.Credentials.jwt(token) and Realm connection issue with RN hot reload

試著忘記壹切 提交于 2021-01-06 03:27:16
问题 I am trying to use Mongo Realm (v10.0.0-beta.9) ; I use a JWT authentication (token being generated by AWS Cognito). It works pretty well since a user has been created (in Mongo Realms Users menu) and I was able to insert a data in my realm. But... 1. Empty user object One strange thing nevertheless: the user I get from the authentication is empty const credentials = Realm.Credentials.custom(jwt) // Authenticate the user const user: Realm.User = await app.logIn(credentials) console.log(

Realm Migration of a String field inside a new RealmList

旧街凉风 提交于 2021-01-04 07:05:31
问题 Conversation class previously had a string field named "message". Now this "message" field is removed and i have added a "RealmList allMessages" inside Conversation class instead of old "message" field. ChatMessage class has a field name "messageText". How can i migrate "message" from Conversation class to "messageText" of list "allMessages"?? public class ChatMessage extends RealmObject implements Parcelable { .... private String messageText; .... } Old Conversation class. public class

Realm Migration of a String field inside a new RealmList

烈酒焚心 提交于 2021-01-04 07:04:03
问题 Conversation class previously had a string field named "message". Now this "message" field is removed and i have added a "RealmList allMessages" inside Conversation class instead of old "message" field. ChatMessage class has a field name "messageText". How can i migrate "message" from Conversation class to "messageText" of list "allMessages"?? public class ChatMessage extends RealmObject implements Parcelable { .... private String messageText; .... } Old Conversation class. public class

How do I delete an item in a collection view with a button in the cell?

痴心易碎 提交于 2021-01-01 09:40:10
问题 It seems like it should be easy to do, but how do I delete the item at the indexPath when the "X" button in the cell is tapped? Do I create an IBAction in the Cell class? If so, how do I pass in the indexPath.item? In some research I have done, I've seen people use notifications and observers, but it seems to be overcomplicated. Can someone provide a basic solution for deleting a cell at the indexPath with a delete button? I am using Realm to persist the items, but I'm having trouble knowing

学习shiro第二天

泄露秘密 提交于 2020-12-31 09:31:40
昨天讲了shiro的认证流程以及代码实现,今天将对这个进行扩展。 因为我们的测试数据是shiro.ini文件中配置的静态数据,但实际上数据应该从数据库中查询出来才合理,因此我们今天讲讲JdbcRealm的使用。 本次需要的jar包如下: commons-beanutils-1.9.3.jar commons-logging-1.2.jar jcl-over-slf4j-1.7.12.jar log4j-1.2.16.jar shiro-all-1.4.1.jar slf4j-api-1.7.25.jar slf4j-log4j12-1.6.4.jar mysql-connector-java-5.1.47.jar mchange-commons-java-0.2.11.jar c3p0-0.9.5.2.jar IniSecurityManagerFactory部分源码: public static final String MAIN_SECTION_NAME = " main " ; public static final String SECURITY_MANAGER_NAME = " securityManager " ; public static final String INI_REALM_NAME = " iniRealm " ; ...... protected

在wildfly 21中搭建cluster集群

对着背影说爱祢 提交于 2020-12-30 00:50:34
简介 wildfly是一个非常强大的工具,我们可以轻松的使用wildfly部署应用程序,更为强大的是,wildfly可以很方便的部署cluster应用。 今天我们通过一个例子来讲解下wildfly如何构建cluster应用。 下载软件和相关组件 假如我们有两个host,一个称为master,一个称为slave,我们需要在两个机子上面安装wildfly,构建成domain模式。然后需要在Domain controller主机上面安装mod_cluster和httpd以组成集群。 首先我们需要下载wildfly-21.0.0.Final.zip,解压之后,运行domain.sh以开启domain模式。 配置domain 我们需要将master配置为domain controller,根据我们之前的文章,首先配置interfaces,我们需要修改domain/configuration/host.xml: <interfaces> <interface name="management" <inet-address value="${jboss.bind.address.management:10.211.55.7}"/> </interface> <interface name="public"> <inet-address value="${jboss.bind.address:10

How can I store a Dictionary with RealmSwift?

痴心易碎 提交于 2020-12-27 08:46:30
问题 Considering the following model: class Person: Object { dynamic var name = "" let hobbies = Dictionary<String, String>() } I'm trying to stock in Realm an object of type [String:String] that I got from an Alamofire request but can't since hobbies has to to be defined through let according to RealmSwift Documentation since it is a List<T> / Dictionary<T,U> kind of type. let hobbiesToStore: [String:String] // populate hobbiestoStore let person = Person() person.hobbies = hobbiesToStore I also

How can I store a Dictionary with RealmSwift?

谁说我不能喝 提交于 2020-12-27 08:41:53
问题 Considering the following model: class Person: Object { dynamic var name = "" let hobbies = Dictionary<String, String>() } I'm trying to stock in Realm an object of type [String:String] that I got from an Alamofire request but can't since hobbies has to to be defined through let according to RealmSwift Documentation since it is a List<T> / Dictionary<T,U> kind of type. let hobbiesToStore: [String:String] // populate hobbiestoStore let person = Person() person.hobbies = hobbiesToStore I also

Kerberos安全工件概述

半城伤御伤魂 提交于 2020-12-18 02:40:16
Cloudera 集群如何使用Kerberos工件,例如principal、keytab和委派令牌。 Cloudera建议使用Kerberos进行身份验证,因为仅原生的Hadoop身份验证仅检查HDFS上下文中的有效成员的 user:group 身份,而不像Kerberos那样对所有网络资源中的用户或服务进行身份验证。与可能更容易部署的其他机制不同,Kerberos协议仅在特定时间段内对发出请求的用户或服务进行身份验证,并且用户可能要使用的每个服务都需要在协议的上下文中使用适当的Kerberos工件。本节描述Cloudera集群如何使用其中一些工件,例如用于用户身份验证的Kerberos principal和Keytab,以及系统如何使用委派令牌在运行时代表已身份验证的用户对作业进行身份验证。 Kerberos principal 每个需要对Kerberos进行身份验证的用户和服务都需要一个 principal ,即一个实体,该实体在可能有多个Kerberos服务器和相关子系统的上下文中唯一标识该用户或服务。principal最多包含三段标识信息,以用户名或服务名(称为“ 主 ” )开头 。通常,principal的主要部分由操作系统中的用户帐户名组成,例如 jcarlos 用于用户的Unix帐户或 hdfs 与主机基础集群节点上的服务守护程序相关联的Linux帐户。