Pythagorean Theorem In Ancient Indian Mathematics : Baudhāyana Sulbasūtra
Many great mathematicians have born in Bharat several thousands of years ago, Ancient Indians invented several theorems in mathematics. Aryabhata the Indian Mathematical Genius lived in (476–550 CE) he worked on approximation of pi() and concluded that its irrational, he has given the formula for the area of a triangle, he discussed the concept of sine etc.
But I would like to discuss one of the most popular theorem Pythagorean theorem, it is named as Pythagorean theorem but it was proved by Ancient Indian Mathematicians several hundreds of years before even Pythagoras born. Just look into the sutra given below.
Install an android mobile application to learn more such interesting facts :Download
dīrghachatursrasyākṣaṇayā rajjuḥ pārśvamānī, tiryagmānī, cha yatpṛthagbhūte kurutastadubhayāṅ karoti.
इसका अर्थ है, किसी आयात का कर्ण क्षेत्रफल में उतना ही होता है, जितना कि उसकी लम्बाई और चौड़ाई होती है। ” बोधायन ” ने ” शुल्ब-सूत्र ” में यह सिद्धान्त दिया है।
A rope stretched along the length of the diagonal produces an area which the vertical and horizontal sides make together
Find out best realtime examples, interesting facts on concepts and all the formulas. The best mobile application for 10+ students (PUC I and II year students)
Find out best realtime examples, interesting facts on concepts and all the formulas. The best mobile application for 10+ students (PUC I and II year students)
Test case template: A template is a structural document and a test case template contains all information required for a test case. Every test engineer will write test cases in test case template, there is nothing called standard test case template. It may vary from company to company and project to project.
It mainly contains the following XLS sheets
HLS Revision History – For High Level Scenario
HLS- Test Scenario Revision
HLS Scenarios
HLS-High Level Test Scenario
HLS Review Comments
HLS Review_Comments_Test_Case
LLS
HLS-High Level Test Scenario_test_case
Test case parameters
Header
Test case name:It is a unique name written by test engineer.For every individual test engineer individual test case name should be written in the below mentioned format.
ProjectName_ModuleName_Scenario
Release name: It is mandatory to mention release name because it helps to identify in which build the issue has been raised.
Requirement number: When BA(Business Analyst) write the requirement number for every individual requirement and unique number will be given to each requirement, so test engineer should copy the requirement number and should write the test case template.
Module name: When BA(Business Analyst) write the requirement, he will also write list of all the module names so test engineer should copy the module name from the requirement and should write the test cases.
Precondition: It is the settings or actions that should be done before executing test cases or step no 1.
Test data: It is a data created by test engineer before executing test case or step no 1.
Example for test data : It is required to create an user account before testing file upload feature.
Test data can be created manually or we can also create test data by executing automation scripts.
Post condition:It is an expected result that we get from the application or when we give the input to the application what ever output we get from the application that is called as post condition.
We mainly use post data when one of the test case is depending on the output of previous test case.
Severity:Test engineer should give severity for each and every individual test cases based on complexity of the feature and importance of feature and importance of feature to the customer business, based on severity test engineer will decide which test cases should be executed first and which test cases executed next.
3 types of severity
1) Critical
2) Major
3) Minor
Test case type: Test engineer should mention which type of testing he is writing in the test case type.
Functional testing
Integration testing
System testing
Smoke testing
Brief description:This field describe the complete information about the test case
Test execution hours:Test engineer should mention how much time he has taken to write and execute the test case ,the value for this field should be enter once of after test execution.
Body
Step no:This field is mainly use to identify each and every step uniquely.
Action or description:It consists of all the navigation steps.
Input:This field consist of the values entered by test engineer while testing the application (URL,Username,password and all +ve and -ve value you entered for every field)
Expected Result:Test engineer will write Expected result by looking in to the requirement the value for this field is entered before test execution.
Actual Result:Test engineer will write actual result while executing the test cases execution. Test engineer will get the actual result from the application.
Status:Test engineer will enter the status of test case as pass or fail after test execution. if expected result is not matching with actual result than test case status is fail else it is pass.
Comments:If the test case is fail then test engineer should enter the reason in the comments stating why the test case is failed.
Footer
Author:Test engineer one who write the test case is called as author.
Reviewer or reviewed by:Test engineer one who reviews the test case which is written by other test engineer is called as reviewer.
Approved by:Test engineer one who approves the test case is called as approved by or approver.
Approval date:The date on which test case is approved is called date.
Test case is a document which gives all possible scenarios for one particular requirement. Ideally a test case document contains set of test data like preconditions,post conditions, actual results and expected results.
Test Scenario : Is a any functionality or a test condition or a test possibility.
Software Testing Life cycle:
Why to write test case:
Test Coverage : Test coverage is a measure of testing and to have better test coverage it is required to write all the tested cases for identified scenario. Ideally the following process will be in action.
Customer will give requirement to developer.
Test engineer has to spend enough time to understand the requirement
Test engineer has to identify all possible scenarios
Test engineer has to write test cases for all identified scenarios.
What are benefits of writing test cases:
Better Consistency : When test cases are written for a test execution, the test engineer work will be organised better and simplified. Let us consider a scenario as an example.
When a release1.0 is being tested using existing test cases, the same test cases can be quickly executed for the next release 1.0.1, having test cases helps to identify issues which impacting the old release, this way we can achieve better consistency in test execution.
2. Avoid training : To avoid training every new test engineer on the product or requirement. Consider the following situation.
Test Engineer write test cases.
Test engineer quits the job
New test engineer joins
It takes lot of effort to explain every module and it takes lot of time for new tester to understand the complete requirement.
But if we write test cases in the beginning, then the newly joined test engineer can test application by looking in to test cases on his own.
Here its not necessary to train him on requirement because, if he execute test cases for couple of release on test cycles he can understand the product.
3. No dependency : To depend on process rather than person. Every company will set their own process
EX: when we get the requirement test engineer should do follow the process.
Understand requirement
identify all scenarios and document.
Prepare a test cases for each scenarios and document.
This process of documenting each and everything will remove the dependency on a person
4. Writing test cases will keep track of all the steps for a particular scenario, this is very important because complicated steps to test a scenario might be difficult to remember always.
Let us consider an example :
Assume that an UI distortion issue will be produced by following steps in a particular scenario
Step1 : Login into Chrome browser ( Hard to remember the platform some times, issue is only in Chrome)
Step 2: Navigate to Home page
Step 3: Select profile from menu in the header
Step 4: Edit First name and Last Name details by giving big string
Step 5: Go back to Home page
Step 6: Navigate to Events page ( only navigating to events page will reproduce the issue)
Step 7: Go back to Home page, the header will shift 100px down leaving black pack at the top
Assuming these steps were not recorded in test cases, when build release 1.0 is given, it is hard to reproduce the same issue again quickly.
If test cases have written, test engineer can easily follow the steps to reproduce and test the issue.
5. Test cases will ensure that complete functional and non functional testing will be done and hence test cases will give complete list of all scenarios to meet the software product quality expectations.
6. The main objective of test case is to exercise every flow in application.
7. To ensure that it satisfies the BRS that is Business Requirement Specification and SRS that is System Requirement Specifications.
8. Test cases will ensure that every functionality working as expected in every possible scenario.
9. Test cases will ensure that all the requirements have been met as per the customer requirement document.
Method getAuthenticateAsList not found Crash – Signup/Signin with Google+ API integration : Java Spring dependency
Crash Report :
SEVERE [http-nio-8080-exec-4] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [Spring] in context with path [/testapp] threw exception [Handler processing failed; nested exception is java.lang.NoSuchMethodError: com.google.api.client.http.HttpHeaders.getAuthenticateAsList()Ljava/util/List;] with root cause java.lang.NoSuchMethodError: com.google.api.client.http.HttpHeaders.getAuthenticateAsList()Ljava/util/List; at com.google.api.client.auth.oauth2.Credential.handleResponse(Credential.java:245) at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:992) at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:410) at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.executeUnparsed(AbstractGoogleClientRequest.java:343) at com.google.api.client.googleapis.services.AbstractGoogleClientRequest.execute(AbstractGoogleClientRequest.java:460) at com.testapp.service.impl.UserServiceImpl.postSignUp(UserServiceImpl.java:147) at com.testapp.controller.UserController.postSignUp(UserController.java:69) at com.testapp.controller.UserController$$FastClassBySpringCGLIB$$6d302bfc.invoke(<generated>) at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:717) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) at org.springframework.aop.framework.adapter.MethodBeforeAdviceInterceptor.invoke(MethodBeforeAdviceInterceptor.java:52) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:653) at com.testapp.controller.UserController$$EnhancerBySpringCGLIB$$99bf7de6.postSignUp(<generated>) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.springframework.web.method.support.InvocableHandlerMethod.invoke(InvocableHandlerMethod.java:215) at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:132) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:104) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandleMethod(RequestMappingHandlerAdapter.java:781) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:721) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:83) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:943) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:877) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:961)
TokenResponse tokenResponse = new TokenResponse();
tokenResponse.setAccessToken(authenticationRequest.getAccessToken());
GoogleCredential cred = new GoogleCredential().setFromTokenResponse(tokenResponse);
/*
* Default HTTP transport to use to make HTTP requests.
*/
HttpTransport TRANSPORT = new NetHttpTransport();
JacksonFactory JSON_FACTORY = new JacksonFactory();
Plus plus = new Plus.Builder(TRANSPORT, JSON_FACTORY, cred).setApplicationName(Constants.APPLICATION_NAME)
.build();
if (plus != null) {
try {
Person userProfile = plus.people().get("me").execute();
if (userProfile != null) {
}
} catch (IOException e) {
e.printStackTrace();
return null;
}
}
Caused by: org.hibernate.cache.NoCacheRegionFactoryAvailableException: Second-level cache is used in the application, but property hibernate.cache.region.factory_class is not given; please either disable second level cache or set correct region factory using the hibernate.cache.region.factory_class setting and make sure the second level cache provider (hibernate-infinispan, e.g.) is available on the classpath.
Solution
Replace POM dependency for net.sf.ehcache : ehcache-core
How innovative ideas on Internet Of Things(IOT) Will change the future
This is an era of IOT, your applications, your gadgets and your vehicles are becoming smarter. Almost every tiniest device you own today is connected to cloud. Already several open source frameworks, operating systems, hardware devices have been evolved to support IOT, It is you who should have an idea and change the future by getting your idea into reality.
No doubt that IOT is gonna change our life style, Several big companies already working on big ideas, SAP is building up their team on IOT, google releasing an OS for IOT, apple already given a hint that they will focus on IOT.
IOT
No doubt that IOT is gonna change our life style, Several big companies already working on big ideas, SAP is building up their team on IOT, google releasing an OS for IOT, apple already given a hint that they will focus on IOT.
5 Innovative Ideas on IOT
5) Future of Transportation – IOT makes transportation better
The SMA research report estimates that by 2020, there will be 8 billion people on the planet and 50 billion connected items with 5 million apps. The opportunity this represents to create new ways to connect, and give consumers more tools to protect their homes and families, is staggering for all industry sectors, including travel.
There is a lot of room to innovate the travel agency – analyze every bit of data, what people like, how people spend time while they are waiting for the arrival of vehicle, what schedules people prefer where people roam within the airport every data matters to plan for any travel agency.
Travel_IOT
A sensor device within the airplane can analyze what people would like to do? make necessary changes in the seating automatically, changes in food without even asking the person based on his past travel records.
How innovative ideas on Internet Of Things(IOT) Will change the future
This is an era of IOT, your applications, your gadgets and your vehicles are becoming smarter. Almost every tiniest device you own today is connected to cloud. Already several open source frameworks, operating systems, hardware devices have been evolved to support IOT, It is you who should have an idea and change the future by getting your idea into reality.
No doubt that IOT is gonna change our life style, Several big companies already working on big ideas, SAP is building up their team on IOT, google releasing an OS for IOT, apple already given a hint that they will focus on IOT.
IOT
No doubt that IOT is gonna change our life style, Several big companies already working on big ideas, SAP is building up their team on IOT, google releasing an OS for IOT, apple already given a hint that they will focus on IOT.
5 Innovative Ideas on IOT
4) Make your kitchen smarter – The IOT Smarter Hotels
This is for big hotels and may not be suitable for your house, a huge data collected on how each dish will be prepared, how the time is being wasted and how the resources are being wasted, all these data helps you to organize everything very well make your hotel more profitable.
not only that based on the past records of the customer the hotel room will be automatically adjusted to specific room temperature and the coffee maker will automatically set to your favorite flavor. The smart display in hotel room will set your favorite tv shows and these all things happen even if you have not visited the same hotel before !
How innovative ideas on Internet Of Things(IOT) Will change the future
This is an era of IOT, your applications, your gadgets and your vehicles are becoming smarter. Almost every tiniest device you own today is connected to cloud. Already several open source frameworks, operating systems, hardware devices have been evolved to support IOT, It is you who should have an idea and change the future by getting your idea into reality.
No doubt that IOT is gonna change our life style, Several big companies already working on big ideas, SAP is building up their team on IOT, google releasing an OS for IOT, apple already given a hint that they will focus on IOT.
IOT
So let me list out some cool IOT ideas which , these are surely pioneering ideas on Internet of Things. Now we shall call it as Internet Of Everything.
5 Innovative Ideas on IOT
3)Analyzing your Food habits and alerting you for dangerous health issues
Food_Sensor_IOT
Definitely if any such innovations happen which makes human life better is really appreciable, what if a sensor collects data on what you eat and collects data on all the changes happening to your body after every kind of food intake. Next time when you go for the same food, your smart phone alerts you about the dangerous health issues which may occur if you eat this food item regularly.
) and concluded that its irrational, he has given the formula for the area of a triangle, he discussed the concept of sine etc.
