Validating the same functionality across devices would be time consuming, using the tool xcode/simulator makes tasks easy to do.
For example: sizes of the screens, font sizes, buttons, can be validated.
Validations can be made on physical device, which is the ultimate step, but in cases where we do not have the devices, a simulator is helpful.
Intro to knowledge objects
Fields – when a search is made the fields are displayed. This helps in narrowing the data which contains only that specific field/keyword. the events,
All the fields can be found in the field side bar, on hover and clicking on the fields specifically, it can be added to the search.
Field extractions
field aliases – normalize data to provide a normal name if the current name is like another field or common!
calculated fields – perform calculations based on existing fields.
lookups – sources like csv can be configured to additional fields and events in search
Event types – same combination over and over- save the search as event type to categorize the data
Tags – key value pairs can be made into tags, can be used in search as event type
note: event types and tags can be also noted in the field side bar
Workflow Actions – interact with external resources to narrow the searches, http get and post to external sources and back to Splunk for secondary searches.
Reports – Repeated search can be saved as reports
Alerts – to receive a notification, search can be saved as alerts
both are used for scheduling
Macros – similar or more complicated syntax – can store entire search strings including commands,
Data models – data sets can be events, can be used in pivot
Name ur objects using Six segmented keys
Primary type of knowledge objects
permissions lay a key role in creating and sharing KO,
When a user creates a ko, it automatically private and only available to that user,
when a power user or admin creates a Ko, it is shared across all users, and has control on other roles by hide/give permissions
only admin has access to allow ko to access across all apps, can edit permissions, can read or edit private objects created by anyone.
Admin can only reassign a ko to user- when the user leaves the org but has knowledge.
Few important tips to take note of
Here we can see about Field Extraction and table formatting
| fields – to make searches more efficient, main part of search
it makes search more efficient if the fields are included or excluded.
| table – like fields- but changes data to tabulated format (transforming command)
fields to be used before using the table command
| dedup – to remove duplicate values form the values displayed in the events/rows
Few of the Stats commands
Chart
| chart count over status
count of a field can be noted in x axis, y always numeric as the data mentioned in x axis can be displayed based on the count.
Questions and Answers:
Reviewing to start on Work product drafts
Early testing is better for the project in dev and in cost savings.
Each dev level has one testing level
Component integration testing- structural, white box,
Impact analysis is used when deciding if a fix is worthwhile.
Functional testing can be performed at any level (4 levels- unit, integration, system integration and acceptance)
ISTQB foundation does not talk about the non-functional as it’s not in scope.
Confirmation testing (retest after the fix has been made) to make sure the issue is not reproduced!
Regression testing is no other parts are impacted by the fix provided in line with the previous statement above (confirmation testing)
impact analysis – fixing the maintenance system is worthwhile.
On Basic words, AB test can be described as a process to allow the team to compare 2 different versions of a feature to learn which is more user friendly and effective and widely used. It helps to derive the business revenue or loss.
For Example: Version A or version B? which could be selected based on specific business measures.
Role:
Ex: Business Analyst, System Analyst
Profile:
I do have a solid 5 years of experience in IT in various technologies and different domains.
The knowledge transition in general in it would be 2 weeks.
Strengths:
Workday:
HCM
Finance
P:ayroll
Student/enrollment/Leave
Advantages:
I have the knowledge required for this role and I am in touch with the existing team on the tickets that are actively working on.
What can i improve
reduce the Gap in the tickets created, analyze on the repeated tickets which does not have a quick resolution,
prioritize and get a solid template of answer to get the tickets resolved quickly.
Roles and Responsibilities
What is expected
What I do every day!
Istqb has a new certification for the mobile application testing, it has the necessary info on the general testing requirements and mindset to validate the mobile app
Usage of our day to day needs in Mobile devices have thrived in recent years, resulting in better and more efficient mobile as in all aspects of business and industry domains.
Validation of the native apps in the Android or iOS devices have increased rapidly.
Considerations:
