Hi All,
With respect to "container-based" deployment patterns related to EI,
following were identified as the first set to be supported and are
currently under development.
Pattern 1: Standalone Integrator Profile with external DB,
Scalable, But Minimum High Availability
Hi all,
I set up the cluster and tested the following scenarios.
- Creating separate profiles (Manager, backend, key manager)
- Enrolling iOS device
- Disenrolling iOS device
- Adding new policies
- Editing policies
- Applying changes in the policies to the already enrolled
Hi Pawan,
Great work. Please prepare the pull request and share it with us. Please
provide the icons of this connector along with the PR. I hope you tested
the connector with out tooling also.
Thanks
On Tue, Jul 25, 2017 at 6:45 PM, Pawan Nayanajith
wrote:
> Hi All,
>
Hi All,
As I mentioned in the previous mails I have completed all the test cases,
and I have manually tested all the methods and the integration testing.
And also I have finished the documentation and created the icon files.
So what do I need to do next? how can I proceed further?
Thank You.
Hi,
I have tested following functionalities for Android Devices.
- Geo Fencing Alerts
- Create Device Type
- Create Device Event
- View Device type
- Create a new device
- Publish device events
Found no issues.
[+] Stable - go ahead and release.
Regards.
On Mon, Jul 24,
Hi all,
I have tested following scenarios in IOS flow.
Super tenant:
- Enrolled a device
- Execute operations - Device Lock, Ring, Notification, Location
- Passcode Policy
- Installed an enterprise application
New Tenant:
- Enrolled a device
- Execute operations - Device
Hi All,
I have tested the following scenarios with super tenant user and a non
super tenant user.
- User Registration
- Android Sense enrollment, Sensor data pushing
- Role Management
- Recovery and reset password
- User Management
- Android operations
- Android enrollment
Hi all,
I tested the following scenarios.
*Android Enterprise Install:*
*> Super Tenant mode: Admin User*
1. Enrolled an Android device as the admin user.
2. Create and publish an Android App.
3. Installed the app to the admin user.
*> Super Tenant mode: Normal user.*
1.
Guys,
Just following up on IoT cluster. How's it looking in terms of testing?
Cheers,
Pubudu.
Pubudu D.P
Senior Software Engineer - QA Team | WSO2 inc.
Mobile : +94775464547
Linkedin: https://uk.linkedin.com/in/pubududp
Medium: https://medium.com/@pubududp
On Tue, Jul 25, 2017 at 5:46 PM,
Hi all;
I have tested the following as Admin in Linux OS
1. Android Virtual Device Download and Enrollment.
2. Virtual Fire Alarm Download and Buzzer operations.
3. Virtual Fire Alarm Real Time Graph.
4. Virtual Fire Alarm Batch analytics Graph.
5. Connected cup instance creation.
6. Connected
Hi all,
I have tested following scenarios for Windows 10.
1. Device enrollment.
2. Add windows operations
3. Create windows policy and apply to the device.
4. Edit Windows policy and done apply changes.
5. Create more policies and set priority and then apply to the device.
6. tested notification
Hi all,
I've tested the following scenarios.
- User Registration
- Android Sense enrollment, Sensor data pushing on tenant / super tenant
account
- Role creation and role assign on tenant / super tenant account
- User password reset on tenant / super tenant account
- User
Hi all,
I have tested the following scenarios for Android.
- Device enrollment
- Device grouping
- Device location
- Device status update
- Device search
- Operations (Mute, Message, Ring, Enterprise-Wipe)
- Policy (Restriction policy)
- App install
- Web-clip install
Hi all,
I have tested following scenarios for iOS.
As an admin:
- Enrolled a device
- Execute operations (Lock, Ring, Notification, Location, Enterprise
wipe)
- Added a policy (restriction)
- Installed an enterprise application
As an user:
- Self sign up an user
-
14 matches
Mail list logo